ICC Marketing Command Center v24

Mission Control

One place for content, footage, ownership, approvals, Danaya handoffs, Zach source mapping, NAS library status, and launch readiness.

Current user lane

What this site is for

This is not a brochure. It is the operating board for turning ICC field footage into useful content. Each person should know where to go, what they own, what is blocked, and what has to happen next.

Launch readiness

Based on setup checklist completion.

Friday target

One complete content packet, not a vague pile of clips.

Proof of workflow

Current cadence

3/wk

Main posts per week, LinkedIn first, IG/Facebook adapted.

Source rule

NAS

Raw footage stays on ICC storage. Metadata and proxies travel.

Mark starts here

Approve claims, set priority, decide what gets published, remove ambiguity.

Zach starts here

Show the folder tree, upload/source-map footage, identify what each clip actually shows.

Danaya starts here

Use clean packets: project facts, selected clips, hooks, platform objective, missing footage requests.

Aaron / ops starts here

Check blockers, review task status, help keep delivery moving.

Plain-English workflow

Zach shoots footage → Zach puts raw files on NAS → Command Center tracks what exists → Danaya gets selected working material → Mark approves technical truth → content gets scheduled → performance gets recorded.

My Work

Today’s rule

Command Board

Owner, deadline, blocker, status. No broken telephone.

NAS Library Map

The website shows the planned structure now. Automatic server scanning is the next backend step.

Required ICC structure

00_ADMIN_SYSTEM/ 01_RAW_ARCHIVE/ 02_PROXIES_FOR_REVIEW/ 03_DANAYA_WORKING/ 04_EXPORTS_FOR_REVIEW/ 05_APPROVED_OUTPUTS/ 06_SOCIAL_PUBLISHING/ 07_WEBSITE_CASE_STUDIES/ 08_MANIFESTS_TAGS/ 99_UNSORTED_INTAKE/

Zach confirmation checklist

Server principle

Raw files stay on ICC NAS. Danaya does not dig through camera dumps. She gets selected working folders, proxies, contact sheets, and clear requests. Google Drive is optional scratch space, not the ICC master system.

Asset Intake

Paste YouTube links, NAS paths, or source notes. This creates a working record.

What counts as a complete asset

Project nameNot just a video title.

Raw source locationNAS path or folder reference.

What it showsPMMA, scraping, shotblast, repair, drain, top coat, etc.

Platform candidateLinkedIn, Instagram, YouTube, website.

Asset Library

Danaya Feed

Clean inputs for creative output. No raw mess.

Copy/paste prompt for Danaya’s AI

Month 1 Calendar

Launch rhythm: three main posts per week. Each post needs owner, asset, approval, platform.

Approval Desk

Mark approves public claims and publish readiness. Danaya can move creative, but technical truth is ICC-owned.

Tracking + Setup Checklist

These items turn the board into a real operating system.

Manual Analytics Entry

Analytics records

Activity Log

Local audit trail until backend database is connected.

Backend Roadmap

v24 clarifies the operating system. v25 connects shared data.

Next technical layer: - Cloudflare Pages Functions / Worker API - Cloudflare D1 database for users, tasks, assets, approvals, events - Cloudflare R2 for proxies, thumbnails, manifests, exports - NAS indexer that generates file manifest, thumbnails, proxies, and rough tags - Cloudflare Access identity mapped to real user roles Working now: the site, roles, task structure, manual intake, local event log, export/import concept. Needs backend: shared multi-user data, automatic NAS scanning, persistent uploads, AI video analysis.