★ Operating System Directory · v2.0

The BridgeApp × Future Club OS.

One operating system. Six deliverables. Every file in this directory works in concert to deliver Phase 2: from awareness to revenue, May–December 2026.

FILES IN OS6 active OWNED BYBlank Canvas BUILD VERSIONv2.0 · May 2026 NEXT REVIEW20 May 2026
★ Master OS Directory Review Card Social Poster Emailer Client Report
01
File inventory
What's in the OS · Where each file lives · What it does
Master
BridgeApp Phase 2 Growth OS
BridgeApp_Phase2_GrowthOS_v2.html
The master dashboard. 12 navigable sections covering all 4 engines, content engine, FC tracker, SA regional map, budget, risks, and team access. The single source of truth.
Owner: DD · Update: Weekly · Format: HTML
Index
OS Directory
BridgeApp_OS_Directory.html
This file. The map of the entire operating system. Shows every file, its owner, update frequency, and how the pieces connect. Bookmark this.
Owner: DD · Update: When files added · Format: HTML
Client
Demo Review Card
BridgeApp_DemoReviewCard.html
Single-page visual sign-off card for the client. The 20 May 2026 approval moment captured as one shareable visual. Includes scope, budget, deliverables, and signature blocks.
Owner: DD · Update: Per phase · Format: HTML
Output
Social Media Poster — FC Launch
BridgeApp_FCLaunch_SocialPoster.html
Brand-aligned Instagram-ratio (1080×1350) social poster announcing Future Club launch. Demonstrates how all visual outputs must conform to BridgeApp guidelines.
Owner: Sememi · Update: Per campaign · Format: HTML
Output
School Competition Emailer
BridgeApp_SchoolCompetition_Emailer.html
Email 1 of the 5-part school competition series — May 2026 invitation. Sent to 400+ IEB pilot schools. Brand-aligned, mobile-responsive, conversion-ready.
Owner: Kefiloe · Update: Per wave · Format: HTML
Report
Phase 2 Client Report
BridgeApp_Phase2_ClientReport.docx
Formal Word document handover. Phase 2 plan summary, engine-by-engine breakdown, budget allocation, risk register, and approval signature page. For client board review.
Owner: DD · Update: Monthly · Format: DOCX
02
Folder structure
Recommended local + cloud organisation
BridgeApp_Phase2_OS/ # Master folder — keep in Google Drive, mirrored locally
├── 01_Master/ # Live operating system
│ ├── BridgeApp_Phase2_GrowthOS_v2.html ★ master dashboard
│ └── BridgeApp_OS_Directory.html this file
├── 02_Client_Deliverables/ # Sign-off & formal docs
│ ├── BridgeApp_DemoReviewCard.html 20 May approval
│ ├── BridgeApp_Phase2_ClientReport.docx board review
│ └── bridgeapp_phase2_handover_2026-05_v1.pdf source PDF
├── 03_Brand_Outputs/ # Every asset goes here
│ ├── social/
│ │ └── BridgeApp_FCLaunch_SocialPoster.html sample
│ ├── email/
│ │ └── BridgeApp_SchoolCompetition_Emailer.html sample
│ ├── btl_pod/ # Pod fabrication briefs (3 files)
│ │ ├── index.html folder map
│ │ ├── pod_fabrication_brief.html ★ critical
│ │ └── school_mou_template.html Kefiloe issues
│ └── brand_lib/ # Logos, fonts, colour swatches (3 files)
│ ├── index.html ★ brand bible
│ ├── colour_swatches.csv Figma/Canva import
│ └── email_signature.html team signatures
├── 04_Engines/ # One folder per engine
│ ├── e01_sales/ # Pathfinder · UniApply · Parent subs (3 files)
│ │ ├── index.html · pathfinder_campaign_brief.html · influencer_brief_template.html
│ ├── e02_future_club/ # Competition · podcast · partners (3 files)
│ │ ├── index.html · competition_manual.html · future_pod_teaser_plan.html
│ ├── e03_school_sales/ # Pods · lounges · golf · merch (3 files)
│ │ ├── index.html · matric_lounge_proposal.html · golf_clinic_run_sheet.html
│ └── e04_systems_data/ # CRM · dashboards · workflows (3 files)
│ ├── index.html · crm_setup_sop.html · weekly_reporting_sop.html
├── 05_Live_Trackers/ # Data layer (5 files)
│ ├── BridgeApp_Phase2_Trackers.xlsx ★ master workbook
│ ├── fc_member_tracker.csv Nono · Friday
│ ├── school_pipeline.csv Kefiloe · daily
│ ├── creative_output_tracker.csv Sememi · daily
│ └── revenue_dashboard.csv DD · weekly
└── 06_Archive/ # Old versions, superseded files
└── BridgeApp_FutureClub_Phase2_MasterOS.html v1 archive
03
Owners & update cadence
Who maintains what · How often it gets updated
Ditshego Ditshego (DD)
Agency Lead · Director
Master OS · Demo Review Card · Phase 2 Client Report · weekly retros · brand QA on all outputs · Friday data review · monthly client check-in
Nono Ditshego
Social Media Intern · 3 days in office
FC Live Tracker (Friday update) · social posts · daily community management · weekly analytics pull · WhatsApp drops · trending audio surfacing
Kefiloe Mametse
School Outreach & Sales Associate
School Pipeline CSV · school emailer waves · pod sign-off MOUs · conference lead capture · golf clinic invites · daily CRM logs
Sememi Mosupye
Junior Brand & Creative Coordinator
Social posters · Reel title cards · email templates · brand library updates · CapCut edits · Canva master template maintenance
04
Access & sync rules
How the team works without re-briefing Claude every session
Step 1 · Set up Claude Project
Create one Claude Project called "BridgeApp × Future Club — Phase 2". Upload: this Directory, the Master OS HTML, the Phase 2 PDF, and the Client Report DOCX. Every future session inherits this context. No more re-briefing.
Setup: DD · Frequency: Once
Step 2 · Mirror to Google Drive
Create the folder structure above in shared Drive. Set "BridgeApp_Phase2_OS" → "Anyone with link can view". Team bookmarks the Drive link. Files stay in sync because they live in one place.
Setup: DD · Frequency: Once
Step 3 · Host Master OS on Netlify
Drag Master OS HTML to netlify.com (drop-deploy). Get a public URL like bridgeapp-os.netlify.app. Share with full team + client. When OS updates, re-drop to replace. URL never changes.
Setup: DD · Frequency: When OS changes
Step 4 · Notion embed (optional)
In Notion: /embed → paste Netlify URL → resize full width. OS now lives inside Notion alongside the team's CRM, content calendar, and SOPs. One workspace, one truth.
Setup: Nono · Frequency: Once
Step 5 · Update workflow
Open the Claude Project → say what changed ("FC pod added at St Mary's" or "Update budget Engine 03"). Claude returns updated file. Replace in Drive → re-deploy Netlify if needed. URL stable. Team sees update immediately.
Owner: DD · Frequency: As needed
Step 6 · Live FC data automation
Make.com pulls BridgeApp backend → Google Sheets → Master OS dashboard updates automatically. Until live (Sep 2026 milestone), Nono updates the FC tracker manually every Friday via the dashboard "Update" form.
Owner: DD + Nono · Live: Sep 2026
05
Brand guardrails — every output
No file leaves Blank Canvas without these passing brand QA
NAVY
#0f2340
BLUE · PATHFINDER
#4a90d9
ORANGE · UNIAPPLY
#e8601c
YELLOW · FUTURE CLUB
#f0b429
Typography
Display: Barlow Condensed Black (900). Used for headlines, numbers, hero copy.
Body: Barlow Regular/Semi-Bold (400/700). Used for paragraphs, captions, UI.
Logo lockup rules
Pathfinder = Blue lockup. UniApply = Orange lockup. Future Club = Yellow lockup. Never mix tier colours within a single product callout.
Tone of voice
Direct. Confident. South African. Never patronising. No tech jargon. Speaks WITH students, not AT them. Says "Future Club" — never "the club" or "FC" in customer-facing copy.
Sales-first rule
Every output has one CTA: sign up · subscribe · register school · download app · book consult. Brand without sale = back to the brief.
BridgeApp × Future Club
Phase 2 OS · Directory v2.0
Blank Canvas Agency
info@blankcanvasafrica.co.za · Reg. 2025/210463/07