From 76de13d1be836d8108fbf9207a44f01847b95891 Mon Sep 17 00:00:00 2001 From: igor vepretski <149789877+vepretski@users.noreply.github.com> Date: Sun, 17 May 2026 17:38:05 +0300 Subject: [PATCH 1/2] Refine 7ya.io command center into executable ops runbook --- 7ya-command-center.md | 213 ++++++++++++++------------ input/7ya-implementation-checklist.md | 49 ++++++ 2 files changed, 164 insertions(+), 98 deletions(-) create mode 100644 input/7ya-implementation-checklist.md diff --git a/7ya-command-center.md b/7ya-command-center.md index e3dc777626a2..ccc1403862b5 100644 --- a/7ya-command-center.md +++ b/7ya-command-center.md @@ -1,98 +1,115 @@ -# 7YA Command Center Operating Brief - -This document consolidates the in-chat 7YA operating strategy into a reusable execution brief. - -## Core Mission - -Position Igor Vepretski / 7YA as a digital-sovereignty builder, social entrepreneur, creator, and systems strategist connecting personal story, StartOn, music, technology, and public influence into one movement. - -## Positioning Lines - -- "Igor Vepretski builds digital systems for people who refuse to stay invisible." -- "7YA is not content. It is digital force." - -Hebrew variants: - -- "איגור ופרצקי בונה מערכות דיגיטליות לאנשים שמסרבים להישאר שקופים." -- "7YA זה לא תוכן. זה כוח דיגיטלי." - -## Brand Pillars - -1. Igor Vepretski — personal authority -2. 7YA.io — digital system / platform -3. StartOn — social proof / mission -4. Music / Artist mode — emotional reach -5. Public leadership — authority and civic voice - -## Campaign 1: "I Was Not Built to Be Managed" - -Primary hook: - -> I was not built to be managed. -> I was built to understand systems — -> then build better ones. - -Hebrew hook: - -> לא נולדתי כדי שינהלו אותי. -> נולדתי להבין מערכות — -> ואז לבנות טובות יותר. - -## 7-Day Rollout - -- Day 1: Identity reset -- Day 2: StartOn authority -- Day 3: Music emotional reach -- Day 4: 7YA.io platform signal -- Day 5: Personal story -- Day 6: Public leadership -- Day 7: Conversion post - -## Daily Execution Rhythm - -- Morning: one sharp text post, one story, one partner outreach -- Afternoon: one value post + 10 meaningful comments -- Evening: one emotional/reel post + one clear CTA - -## Content Language Rules - -Use build-system framing rather than influencer phrasing. - -- "The system is live." -- "This is the build log." -- "Help build infrastructure." -- "Youth do not need slogans. They need tools." -- "New signal loading." - -## Immediate Post (Today) - -> I am consolidating everything. -> -> StartOn. -> 7YA. -> Music. -> AI. -> Public voice. -> Personal story. -> -> It was never separate. -> -> It was one system learning how to speak. -> -> Now it speaks. -> -> #7YA🥷 - -Visual direction: dark cinematic portrait, minimal text, small `7YA🥷` mark. - -## Strategy Filter for Every Asset - -For any incoming idea, run this checklist: - -1. Strategic purpose -2. Matching brand pillar -3. Public-facing signal -4. Partner-facing meaning -5. Algorithm-facing metadata pattern -6. Next action -7. Net reinforcement for 7YA / StartOn / Igor +# 7ya.io Command Center + +Operational command document for managing **7ya.io** as a production system with three linked tracks: +- platform reliability, +- civic intake operations, +- audience and trust growth. + +## Outcome Definition + +7ya.io is considered "managed" only when all three tracks are active: +1. **System is stable** (fast, reachable, monitored). +2. **Intake is trustworthy** (lawful collection, triage, anonymization, follow-up). +3. **Public loop is alive** (clear updates, evidence briefs, accountable escalation). + +## 72-Hour Plan + +### Hour 0–12: Platform hardening +- Confirm domain DNS, SSL validity, and uptime monitoring. +- Publish status owner and incident contact channel. +- Verify form and dashboard authentication boundaries. +- Add/update public disclosure page: + - what is collected, + - legal basis and purpose, + - retention window, + - deletion request process. + +### Hour 12–24: Controlled data intake +- Open intake to 15–20 trusted participants first. +- Accept only structured reports with required minimum fields. +- Start moderation queue with statuses: + - `green` usable, + - `yellow` incomplete, + - `red` unsafe/unverifiable, + - `blue` approved for anonymized publication. + +### Hour 24–48: First operational brief +- Produce preliminary snapshot with mandatory disclaimer: + - "Initial intake, not a representative sample." +- Report only verified aggregates: + - leading neighborhoods, + - leading issue types, + - recurring time windows, + - previous authority contact rate. +- Prepare one concise escalation letter with anonymized annex. + +### Hour 48–72: Recurring operating cycle +- Run repeatable daily loop: + - intake → triage → anonymize → summarize → escalate → follow up. +- Assign named owner for each stage. +- Start weekly KPI tracking and publish first transparent operations note. + +## Minimum Data Contract + +Required fields: +- `report_id` +- `created_at` +- `city` +- `neighborhood` +- `zone_description` +- `issue_type` +- `incident_time_window` +- `affected_group` +- `contacted_authority` (yes/no + channel) +- `callback_consent` (yes/no) +- `anonymized_publish_consent` (yes/no) +- `validation_status` (green/yellow/red/blue) +- `urgency_level` (low/medium/high) +- `follow_up_owner` +- `follow_up_status` + +Never collect: +- ID numbers, +- exact home addresses, +- minor-identifying details, +- named accusations against private individuals. + +## Operating Rules (Non-Negotiable) +1. Legal and factual only. +2. No personally identifying publication. +3. No unverified accusations. +4. No inflated claims from early data. +5. Every public output must state: knowns, unknowns, next action. +6. Emergency risk is routed to official emergency services first. + +## Ownership Matrix + +- **Ops Lead**: uptime, incidents, release sign-off. +- **Data Lead**: triage quality, deduplication, export controls. +- **Privacy Lead**: consent policy, deletion requests, publication review. +- **Community Lead**: inbound communication and callback scheduling. +- **Escalation Lead**: municipality/police liaison letters and follow-up log. + +## Weekly KPIs +- raw_submissions +- usable_submissions (`green + blue`) +- unique_mapped_zones +- callback_consent_rate +- escalations_sent +- responses_received +- median_triage_time +- median_days_to_follow_up + +## Public Update Template + +> We are collecting initial neighborhood safety reports to identify patterns and support structured follow-up with relevant authorities. +> This is a preliminary intake phase and not yet a representative sample. +> Identifying details are removed before any public sharing. + +## Escalation Trigger +Escalate when: +- multiple independent reports converge on the same zone and timeframe, +- vulnerable populations are repeatedly affected, +- risk indicators suggest urgent intervention. + +7ya.io is a civic coordination layer and does not replace emergency responders or legal authorities. diff --git a/input/7ya-implementation-checklist.md b/input/7ya-implementation-checklist.md new file mode 100644 index 000000000000..cc099eecd686 --- /dev/null +++ b/input/7ya-implementation-checklist.md @@ -0,0 +1,49 @@ +# 7ya.io Implementation Checklist + +## A. Platform Reliability +- [ ] DNS and SSL verified. +- [ ] Uptime monitor enabled with alert recipient. +- [ ] Incident contact path documented. +- [ ] Admin/dashboard routes require authentication. + +## B. Intake Product +- [ ] Reporting form is mobile-optimized. +- [ ] Required fields match minimum data contract. +- [ ] Status workflow enabled (`green`, `yellow`, `red`, `blue`). +- [ ] CSV export restricted to verified records only. + +## C. Privacy and Compliance +- [ ] Privacy notice published and linked in form footer. +- [ ] Consent checkbox: callback communication. +- [ ] Consent checkbox: anonymized public usage. +- [ ] Retention and deletion process documented. +- [ ] No excessive/sensitive fields collected. + +## D. Daily Operations +- [ ] Triage owner assigned. +- [ ] Data quality owner assigned. +- [ ] Community callback owner assigned. +- [ ] Escalation owner assigned. +- [ ] End-of-day audit log captured. + +## E. Communications +- [ ] Public intake message prepared. +- [ ] Telegram broadcast format prepared. +- [ ] Hebrew/Russian response snippets ready. +- [ ] Preliminary-disclaimer line included in all early outputs. + +## F. Evidence Brief (First 24–48h) +- [ ] Total raw reports. +- [ ] Total usable reports. +- [ ] Top 3 areas. +- [ ] Top 3 issue categories. +- [ ] Peak time windows. +- [ ] Prior authority-contact count. +- [ ] 3 clear actions requested from relevant authority. + +## G. Exit Criteria: "Managed" +- [ ] System uptime and incident owner confirmed. +- [ ] Intake and triage loop running daily. +- [ ] One preliminary brief published with disclaimer. +- [ ] One formal escalation sent with anonymized annex. +- [ ] Follow-up tracker active with owner and deadlines. From 20b0c9b6bc73c1275adff54865f151885f8d3433 Mon Sep 17 00:00:00 2001 From: igor vepretski <149789877+vepretski@users.noreply.github.com> Date: Sun, 17 May 2026 17:43:41 +0300 Subject: [PATCH 2/2] Resolve command center drift and add execution cadence --- 7ya-command-center.md | 20 ++++++++++++++++++++ input/7ya-implementation-checklist.md | 6 +++++- 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/7ya-command-center.md b/7ya-command-center.md index ccc1403862b5..a085444ed1b7 100644 --- a/7ya-command-center.md +++ b/7ya-command-center.md @@ -90,6 +90,26 @@ Never collect: - **Community Lead**: inbound communication and callback scheduling. - **Escalation Lead**: municipality/police liaison letters and follow-up log. + +## Command Cadence (Daily) + +Run this fixed cadence every day: +1. **09:00 UTC — Systems check**: uptime, SSL, auth, ingestion health. +2. **12:00 UTC — Triage checkpoint**: clear `yellow` backlog and reclassify. +3. **16:00 UTC — Escalation window**: send/track authority follow-ups. +4. **20:00 UTC — Public note**: publish anonymized, evidence-based update. + +If a checkpoint is missed, log cause and recovery action in the follow-up tracker. + +## First Week Deliverables +- Day 1: intake live + privacy notice live + role assignment complete. +- Day 2: first 30 raw reports triaged and deduplicated. +- Day 3: first preliminary brief published with disclaimer. +- Day 4: first escalation letter sent with anonymized annex. +- Day 5: response tracker updated and callback queue processed. +- Day 6: KPI baseline captured. +- Day 7: weekly operations report published. + ## Weekly KPIs - raw_submissions - usable_submissions (`green + blue`) diff --git a/input/7ya-implementation-checklist.md b/input/7ya-implementation-checklist.md index cc099eecd686..cf801fe76660 100644 --- a/input/7ya-implementation-checklist.md +++ b/input/7ya-implementation-checklist.md @@ -41,7 +41,11 @@ - [ ] Prior authority-contact count. - [ ] 3 clear actions requested from relevant authority. -## G. Exit Criteria: "Managed" +## G. Release Hygiene +- [ ] No merge markers present (`<<<<<<<`, `=======`, `>>>>>>>`). +- [ ] Command center and checklist versions are aligned. + +## H. Exit Criteria: "Managed" - [ ] System uptime and incident owner confirmed. - [ ] Intake and triage loop running daily. - [ ] One preliminary brief published with disclaimer.