@hybridlabor-api/aos 4.9.0 → 4.11.0

package/installer.js

@@ -2921,7 +2921,7 @@ async function installMcpsForTarget(paths, ctx) {
     }
     log.step(`Installed selected MCP servers to ${mcpCodeTarget}`);
 
-    const nodeMcps = ['adobe_uxp_mcp', 'unreal_mcp', 'tdmcp', 'touchdesigner-mcp', 'davinci-resolve-mcp', 'after-effects-mcp', 'computer-use-mcp'];
+    const nodeMcps = ['adobe_uxp_mcp', 'unreal_mcp', 'tdmcp', 'touchdesigner-mcp', 'davinci-resolve-mcp', 'after-effects-mcp', 'computer-use-mcp', 'mcsc'];
     for (const mcpFolder of nodeMcps.filter(m => selectedMcps.includes(m))) {
         const targetFolder = path.join(mcpCodeTarget, mcpFolder);
         if (fs.existsSync(path.join(targetFolder, 'package.json'))) {
@@ -3469,13 +3469,17 @@ function compileCodexAgents(agents, targetDir, pipelineConfig = null) {
 
 
 function injectHarnessRules() {
-    const geminiMdSrc = path.join(srcDir, 'GEMINI.md');
+    const rulesMdSrc = path.join(srcDir, 'RULES.md');
     const agentsMdSrc = path.join(srcDir, '.agents', 'agents.md');
 
-    if (fs.existsSync(geminiMdSrc)) {
-        installStep(`install GEMINI.md to ${path.join(geminiDir, 'GEMINI.md')}`, () => {
-            copyDirRecursiveSync(geminiMdSrc, path.join(geminiDir, 'GEMINI.md'));
-            log.step(`Installed GEMINI.md to ${path.join(geminiDir, 'GEMINI.md')}`);
+    if (fs.existsSync(rulesMdSrc)) {
+        installStep(`install RULES.md to ${path.join(geminiDir, 'RULES.md')}`, () => {
+            copyDirRecursiveSync(rulesMdSrc, path.join(geminiDir, 'RULES.md'));
+            // Keep GEMINI.md in sync for backwards compatibility with Antigravity CLI harnesses
+            try {
+                fs.copyFileSync(rulesMdSrc, path.join(geminiDir, 'GEMINI.md'));
+            } catch (e) { logDebug(e, 'sync GEMINI.md fallback'); }
+            log.step(`Installed RULES.md to ${path.join(geminiDir, 'RULES.md')}`);
         }, 'The harness injection below still runs.');
 
         // Dispatcher scripts must land in ~/.claude/workflows/, because that is
@@ -3495,7 +3499,7 @@ function injectHarnessRules() {
 
         const startcycleWorkflowSrc = path.join(srcDir, '.agents', 'workflows', 'startcycle.md');
         const sources = installStep('read the global rule sources', () => ({
-            globalRules: fs.readFileSync(geminiMdSrc, 'utf8'),
+            globalRules: fs.readFileSync(rulesMdSrc, 'utf8'),
             startcycleContent: fs.existsSync(startcycleWorkflowSrc) ? fs.readFileSync(startcycleWorkflowSrc, 'utf8') : '',
             agentsMdContent: fs.existsSync(agentsMdSrc) ? fs.readFileSync(agentsMdSrc, 'utf8') : ''
         }), 'Cursor, Claude, Copilot and Codex keep their current instruction files.');
@@ -3670,6 +3674,106 @@ function injectHarnessRules() {
     }
 }
 
+// Copy the OpenCode plugin + command payload and register both in
+// opencode.jsonc. This is the single copy site: the Quick Update path
+// (injectHarnessRules -> installGlobalHooks) and the fresh-install path
+// (universalHarnessSync -> syncOpencodeConfig) both reach it, so a version that
+// adds or changes the plugin can no longer ship to one path and miss the other.
+//
+// `data` is mutated in place when the caller owns the config write (Universal
+// Sync merges MCP servers in the same pass and writes once). When `data` is
+// omitted the function loads and saves the config itself, which is what lets the
+// Quick Update path register the plugin as well as copy it.
+function installOpencodePlugin({ targetHome = homeDir, configPath = null, data = null } = {}) {
+    const opencodeDir = configPath
+        ? path.dirname(configPath)
+        : (process.platform === 'win32'
+            ? path.join(process.env.APPDATA || targetHome, 'opencode')
+            : path.join(targetHome, '.config', 'opencode'));
+
+    const pluginSrc = path.join(srcDir, '.opencode', 'plugins', 'bdb-aos.js');
+    let pluginInstalled = false;
+    if (fs.existsSync(pluginSrc)) {
+        const pluginDest = path.join(opencodeDir, 'plugins', 'bdb-aos.js');
+        try {
+            fs.mkdirSync(path.dirname(pluginDest), { recursive: true });
+            fs.copyFileSync(pluginSrc, pluginDest);
+            try { fs.chmodSync(pluginDest, 0o644); } catch (e) { logDebug(e, 'chmod opencode plugin'); }
+            pluginInstalled = true;
+            log.step(`Installed OpenCode plugin to ${pluginDest}`);
+        } catch (e) {
+            log.warn(`Could not install OpenCode plugin: ${e.message}`);
+        }
+    }
+
+    // Slash-command payloads. Without these the /startcycle-graph command has no
+    // native resolution and only survives as a raw-text match in the plugin.
+    const commandsSrc = path.join(srcDir, '.opencode', 'commands');
+    if (fs.existsSync(commandsSrc)) {
+        try {
+            copyDirRecursiveSync(commandsSrc, path.join(opencodeDir, 'commands'));
+            log.step(`Installed OpenCode commands to ${path.join(opencodeDir, 'commands')}`);
+        } catch (e) {
+            log.warn(`Could not install OpenCode commands: ${e.message}`);
+        }
+    }
+
+    if (!pluginInstalled) return data;
+
+    const ownsWrite = data === null;
+    let beforeSerialized = null;
+    if (ownsWrite) {
+        if (!configPath) return data;
+        const existing = readJsoncFile(configPath) || {};
+        // Snapshot before mutating: `data` becomes the same object, so
+        // comparing afterwards would always report "unchanged".
+        beforeSerialized = JSON.stringify(existing, null, 2);
+        data = existing;
+    }
+
+    // Register the plugin.
+    if (!Array.isArray(data.plugin)) data.plugin = [];
+    const pluginPathNormalized = path.join(opencodeDir, 'plugins', 'bdb-aos.js').replace(/\\/g, '/');
+    const alreadyRegistered = data.plugin.some(p => {
+        const str = typeof p === 'string' ? p : (Array.isArray(p) ? p[0] : '');
+        return str.includes('bdb-aos');
+    });
+    if (!alreadyRegistered) data.plugin.push(pluginPathNormalized);
+
+    // Skill paths. `.agents/skills` stays project-relative on purpose: it is the
+    // per-project contract, and OpenCode resolves it against each project, so it
+    // is meaningful in a bootstrapped project and inert elsewhere. The absolute
+    // ~/.agents/skills is added only when it is really there -- registering a
+    // path that does not exist is the defect this replaces.
+    const homeAgentsSkills = path.join(targetHome, '.agents', 'skills').replace(/\\/g, '/');
+    const desired = ['.agents/skills'];
+    if (fs.existsSync(homeAgentsSkills)) desired.unshift(homeAgentsSkills);
+    if (!data.skills || typeof data.skills !== 'object' || !Array.isArray(data.skills.paths)) {
+        data.skills = { paths: desired.slice() };
+    } else {
+        for (const p of desired) {
+            if (!data.skills.paths.includes(p)) data.skills.paths.push(p);
+        }
+    }
+
+    if (ownsWrite) {
+        // Write only on a real change. readJsoncFile strips comments, so
+        // serialising an unchanged config would silently eat a user's comments
+        // for no benefit. When a write is genuinely needed the comments in the
+        // file are lost -- acceptable, and worth saying out loud in the PR.
+        const serialized = JSON.stringify(data, null, 2);
+        if (beforeSerialized === serialized) return data;
+        try {
+            fs.mkdirSync(path.dirname(configPath), { recursive: true });
+            fs.writeFileSync(configPath, serialized, { mode: 0o600 });
+            try { fs.chmodSync(configPath, 0o600); } catch (e) { logDebug(e, 'chmod opencode config'); }
+        } catch (e) {
+            log.warn(`Could not write ${configPath}: ${e.message}`);
+        }
+    }
+    return data;
+}
+
 // Deliver the hook scripts to ~/.claude/hooks/ and wire them in settings.json.
 // Both the full install and Quick Update funnel through here. Quick Update used
 // to do neither: it refreshes skills and submodules, but hooks are harness
@@ -3729,22 +3833,15 @@ function installGlobalHooks({ targetHome = homeDir, targetGemini = geminiDir } =
     mergeCodexTomlHooks(path.join(targetHome, '.codex', 'config.toml'));
 
     // 4. OpenCode CLI
-    const opencodeDir = process.platform === 'win32'
-        ? path.join(process.env.APPDATA || targetHome, 'opencode')
-        : path.join(targetHome, '.config', 'opencode');
-    const opencodePluginSrc = path.join(srcDir, '.opencode', 'plugins', 'bdb-aos.js');
-    if (fs.existsSync(opencodePluginSrc)) {
-        const opencodePluginsDir = path.join(opencodeDir, 'plugins');
-        const opencodePluginDest = path.join(opencodePluginsDir, 'bdb-aos.js');
-        try {
-            fs.mkdirSync(opencodePluginsDir, { recursive: true });
-            fs.copyFileSync(opencodePluginSrc, opencodePluginDest);
-            try { fs.chmodSync(opencodePluginDest, 0o644); } catch (e) { logDebug(e, 'chmod opencode plugin'); }
-            log.step(`Installed OpenCode plugin to ${opencodePluginDest}`);
-        } catch (e) {
-            log.warn(`Could not install OpenCode plugin: ${e.message}`);
-        }
-    }
+    installOpencodePlugin({
+        targetHome,
+        configPath: path.join(
+            process.platform === 'win32'
+                ? path.join(process.env.APPDATA || targetHome, 'opencode')
+                : path.join(targetHome, '.config', 'opencode'),
+            'opencode.jsonc'
+        ),
+    });
 
     // 5. Global CLI launcher binaries (aos-config, aos-dashboard, aos-uninstall)
     installGlobalBinaries();
@@ -4774,47 +4871,10 @@ async function universalHarnessSync(primaryMcpConfigPath, installedModules = [])
                 }
             }
 
-            // Wire BDB AOS Plugin for OpenCode
-            const opencodeDir = path.dirname(targetPath);
-            const pluginsDir = path.join(opencodeDir, 'plugins');
-            const pluginFile = path.join(pluginsDir, 'bdb-aos.js');
-            const pluginSrc = path.join(srcDir, '.opencode', 'plugins', 'bdb-aos.js');
-
-            try {
-                if (fs.existsSync(pluginSrc)) {
-                    fs.mkdirSync(pluginsDir, { recursive: true });
-                    fs.copyFileSync(pluginSrc, pluginFile);
-                    try { fs.chmodSync(pluginFile, 0o644); } catch (e) { logDebug(e, 'chmod pluginFile'); }
-                }
-            } catch (pluginErr) {
-                log.warn(`Could not install OpenCode plugin: ${pluginErr.message}`);
-            }
-
-            // Register plugin in opencode.jsonc if plugin file exists
-            if (fs.existsSync(pluginFile)) {
-                if (!Array.isArray(data.plugin)) {
-                    data.plugin = [];
-                }
-                const pluginPathNormalized = pluginFile.replace(/\\/g, '/');
-                const alreadyRegistered = data.plugin.some(p => {
-                    const str = typeof p === 'string' ? p : (Array.isArray(p) ? p[0] : '');
-                    return str.includes('bdb-aos');
-                });
-                if (!alreadyRegistered) {
-                    data.plugin.push(pluginPathNormalized);
-                }
-            }
-
-            // Register skills paths for OpenCode
-            if (!data.skills || typeof data.skills !== 'object') {
-                data.skills = { paths: [".agents/skills"] };
-            } else if (Array.isArray(data.skills.paths)) {
-                if (!data.skills.paths.includes(".agents/skills")) {
-                    data.skills.paths.push(".agents/skills");
-                }
-            } else {
-                data.skills.paths = [".agents/skills"];
-            }
+            // Wire BDB AOS Plugin for OpenCode. `data` is handed in because this
+            // function owns the write -- it merges MCP servers in the same pass.
+            // homeDir matches how the opencode harness entry builds its path.
+            installOpencodePlugin({ targetHome: homeDir, configPath: targetPath, data });
 
             fs.mkdirSync(path.dirname(targetPath), { recursive: true });
             fs.writeFileSync(targetPath, JSON.stringify(data, null, 2), { mode: 0o600 });
@@ -4914,7 +4974,7 @@ async function runQuickUpdate(installState) {
     pruneRemovedSkills(_sessionManifest);
     s.stop('Skills refreshed');
 
-    // Everything injectHarnessRules() delivers -- GEMINI.md, the dispatcher
+    // Everything injectHarnessRules() delivers -- RULES.md, the dispatcher
     // workflows the skills point at, the compiled subagent definitions, the
     // harness rule files and the gate + memory hooks -- used to be
     // fresh-install-only. v4.4.1 split just the hooks out of it for Quick
@@ -5087,7 +5147,7 @@ async function main() {
         path.join(srcDir, '.cursor'),
         path.join(srcDir, '.github'),
         path.join(srcDir, '.codex-plugin'),
-        path.join(srcDir, 'GEMINI.md'),
+        path.join(srcDir, 'RULES.md'),
         path.join(srcDir, 'AGENTS.md'),
         path.join(srcDir, 'CLAUDE.md'),
         path.join(srcDir, 'CODEX.md'),
@@ -5493,6 +5553,7 @@ module.exports = {
     mergeCodexHooks: mergeCodexTomlHooks,
     mergeCodexTomlMcpServers,
     installGlobalHooks,
+    installOpencodePlugin,
     installProjectHarness,
     promptMcpSelection,
     mirrorMcpServersTo,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hybridlabor-api/aos",
-  "version": "4.9.0",
+  "version": "4.11.0",
   "description": "AOS — A Curated AI AGENT OS. Optimized agent skills and add-ons like memB, OpenWiki, Heimdall Token Saver, and Godmode architectures.",
   "main": "installer.js",
   "engines": {
@@ -27,7 +27,7 @@
     "plugin:build": "node scripts/build-plugin-manifest.mjs",
     "plugin:check": "node scripts/build-plugin-manifest.mjs --check",
     "doctor": "node bin/aos-doctor.mjs",
-    "test": "node scripts/validate-skills.mjs --selftest && node scripts/validate-skills.mjs && node scripts/build-plugin-manifest.mjs --check && node tests/aos-store.test.mjs && node tests/aos-doctor.test.mjs && node tests/build-plugin-manifest.test.mjs"
+    "test": "node scripts/validate-skills.mjs --selftest && node scripts/validate-skills.mjs && node scripts/build-plugin-manifest.mjs --check && node --test tests/opencode-graph-gate.test.js && node --test tests/cross-harness-hooks.test.js && node tests/aos-store.test.mjs && node tests/aos-doctor.test.mjs && node tests/build-plugin-manifest.test.mjs"
   },
   "publishConfig": {
     "access": "public"
@@ -45,7 +45,7 @@
     "bin/",
     "lib/",
     "mcp_config.json",
-    "GEMINI.md",
+    "RULES.md",
     "CODEX.md",
     "CLAUDE.md",
     "THIRD_PARTY_NOTICES.md",

package/skills/basic/bdb-eventagency-skill/SKILL.md

@@ -0,0 +1,252 @@
+---
+name: bdb-eventagency-skill
+description: "Use for event agency operations: client intake, project scoping, vendor management, crew coordination, production planning, pre-show logistics, and post-show wrap. Delegates technical execution to godmode-eventtech and bdbmediastorm."
+category: media-eventtech
+source: talkvalue/event-agency-skills
+---
+
+# BDB Event Agency Skill
+
+The **agency-ops layer** for Hybridlabor Global — the business and production-coordination side of running an event company. This skill owns everything that happens *before, around, and after* the show. It does not own the technical execution itself.
+
+Techniques adapted from [talkvalue/event-agency-skills](https://github.com/talkvalue/event-agency-skills) (Apache-2.0). Prose only — no upstream code, no scripts, no dependencies.
+
+---
+
+## 1. Routing Table
+
+| Task | Route to |
+|---|---|
+| Signal flow, protocol binding, OSC/DMX, hardware limits, MCP orchestration | `godmode-eventtech` |
+| Live show architecture brainstorming, creative direction | `bdbmediastorm` |
+| Lighting cue execution, patch, playback | `bdb-grandma3-mcp` |
+| Video clip, layer, and output control | `bdb-resolume-mcp` |
+| 3D scene, render, spatial build | `godmode-3d-creation` |
+| Client intake, scoping, budget, scheduling, vendor, crew, pre-show logistics, post-show wrap | **stay in this skill** |
+
+**Boundary rule:** if the question is *"what should this look like"* or *"what signal goes where"*, route out. If it is *"who is bringing it, what did they promise, and what happens when they don't"*, it stays here. This skill never issues a technical execution instruction — it routes.
+
+---
+
+## 2. Client & Project Intake
+
+An event request is not a booking until these are known. Anything guessed here becomes a change order later.
+
+### Required fields before committing
+
+| Field | Why it is required | If missing |
+|---|---|---|
+| **Date** (and whether date or time is flexible) | Drives every downstream deadline in this skill | Cannot scope. Ask first. |
+| **Venue** (named, or shortlist with constraints) | Venue holds all vendor access; determines power, load-in window, noise curfew | Cannot plan load-in or vendor sequencing |
+| **Brief** — what must happen, who must be in the room | Distinguishes an event from a venue rental | Ask: *"What does success look like when the last guest leaves?"* |
+| **Budget range** — a band, not a number | Drives the action policy: which classes are `never` vs `criteria` | Do not quote. Scope verbally only. |
+| **Technical rider** | AV, staging, power, network, FOH position | Route to `godmode-eventtech` for feasibility |
+| **Attendance estimate** | Drives catering counts, staffing, registration, capacity | Cannot close catering or staffing |
+| **Client contact + decision authority** | Who can actually say yes | Every later "we'll confirm" is a no |
+
+### Scoping questions to ask before any commitment
+
+1. **Who signs?** Not "the client" — a name. The person who can approve a change order on show day.
+2. **What is non-negotiable?** Date, venue, budget, talent, or brand. Everything else is negotiable; know which one is not.
+3. **What has been promised already, in writing, to anyone?** Sponsors and speakers hold commitments that predate you.
+4. **What is the failure mode we are least able to absorb?** Late AV is a catastrophe; late florals are an inconvenience. Escalation urgency (§4) follows from this answer.
+5. **Is there a technical rider yet?** If not, that is a Phase 0 action, not a show-week action.
+
+### Scope statement rule
+
+Produce a written scope before any deposit. It must name: date, venue, attendance band, the ten action classes with their modes (default-deny — see `.aos/factory.yaml`), what is explicitly out of scope, and the change-order trigger. A scope without an out-of-scope list will be expanded by the client by default.
+
+---
+
+## 3. Inbox Triage
+
+Run this at the start of a working day on an active event, before a production meeting, or after time away. It produces a **point-in-time snapshot**, not a live feed.
+
+### Stakeholder classification
+
+| Type | Key signals | Default tier |
+|---|---|---|
+| **Vendor** | AV, catering, security, decor, transport, staffing, rentals, print | 2 |
+| **Client** | Contracting organisation, corporate domain, C-suite/VP | 2 |
+| **Sponsor** | Activation budget or in-kind contribution — **distinct from the client even when the client also sponsors** | 3 |
+| **Speaker** | Bureau domain, rider, session, keynote, bio/headshot request | 3 |
+| **Venue** | Hotel, convention centre, outdoor site, venue coordinator, venue-employed catering manager | 2 |
+| **Internal** | Own domain, team aliases, automated notifications | 3 |
+
+When a thread is ambiguous, default to the type with the higher production impact: **Vendor > Venue > Speaker** for operational threads.
+
+### Priority tiers
+
+| Tier | Label | Response window | Criteria |
+|---|---|---|---|
+| **1** | Immediate | 1–2 hours | Blocked deliverable, payment deadline within 48h, client waiting on confirmation, venue or vendor escalation, load-in unresolved within 72h of the event |
+| **2** | Today | Business hours | Advancing information requests, assets for review, draft approvals, speaker logistics more than 72h out |
+| **3** | Tracking | None | FYIs, confirmations of receipt, vendor acknowledgements, threads you are CC'd on |
+
+### Temporal override rules — apply before finalising tiers
+
+These override the table above:
+
+- Any vendor email mentioning **load-in, install, delivery window, or rider compliance** is Tier 1 if the event is within 14 days.
+- Any client email containing **a question in subject or body** is Tier 1.
+- Any Tier 1 thread with **no outbound reply in 24h+** escalates to flagged regardless of its original tier.
+
+**Rationale:** the tier table is a prior. The overrides exist because the failure mode of event email is a request that looked like an FYI and was not one.
+
+### Output shape
+
+A dated digest containing: event name, timestamp, event phase, period covered, counts per tier, then the tier-1 and tier-2 threads with the *specific* action each needs and who owns it. Every extracted action item must be one of:
+
+- **[OUR ACTION]** — a commitment we made, with a date
+- **[AWAITING]** — a commitment someone else made, with a date
+- **[APPROVAL NEEDED]** — a decision only the client can make
+
+Never mix these three. An action with no owner is not an action item.
+
+---
+
+## 4. Vendor Management
+
+Track **existing** vendor commitments and deliverables. This skill does not source vendors, negotiate contracts, or process payments.
+
+### Vendor types, lead times, and failure impact
+
+| Type | Typical lead time | Failure impact |
+|---|---|---|
+| AV / Technical | 2–4 weeks | **Critical** — no AV, no event |
+| Venue | Contracted months ahead | **Critical** — venue holds all vendor access |
+| Catering / F&B | 2–3 weeks (final count 72h) | High — dietary and count changes cascade |
+| Transport / Logistics | 1–2 weeks | High — gear and people movement |
+| Security | 1–2 weeks | High — compliance and safety |
+| Entertainment / Talent | Rider-dependent | High — contracted, non-fungible |
+| Decor / Floral | 1–2 weeks | Medium — visual, not operational |
+| Staffing Agencies | 1–2 weeks | Medium — replaceable if flagged early |
+| Signage / Print | 5–10 business days | Medium — wayfinding and branding |
+| Rentals | 1 week | Medium — tables, chairs, linens |
+
+### Phase-based urgency
+
+Urgency is relative to **event proximity**, never absolute time. The same 48-hour silence is fine in month one and a production risk in advance week.
+
+| Phase | Window | Overdue threshold | Escalation speed |
+|---|---|---|---|
+| Normal | T-30 and out | 48h no response | Standard: email → wait → follow-up |
+| Planning | T-30 to T-8 | 24h no response | Accelerated: email → same-day follow-up |
+| Advance | T-7 to T-2 | 12h no response | Urgent: email → phone within 4h |
+| Load-in | T-1 | 2h no response | Emergency: phone immediately, escalate to production lead |
+| Show day | T-0 | 1h no response | Emergency: phone + contingency activation |
+
+### Item status taxonomy
+
+| Status | Meaning |
+|---|---|
+| **OVERDUE** | Past deadline, no confirmation |
+| **AT RISK** | Deadline approaching, last contact exceeds the phase threshold |
+| **ON TRACK** | Confirmed, or within the normal response window |
+| **BLOCKED** | **Waiting on us, not the vendor** |
+
+**BLOCKED items are the most important row in the table and are routinely under-reported.** When a vendor is waiting on our headcount, floor plan, or approval, that is our team's problem. Surface it first.
+
+### Escalation path
+
+| Attempt | AV / Venue / Catering | Decor / Signage / Rentals | Staffing / Transport |
+|---|---|---|---|
+| 1st | Follow-up email quoting the original request | Follow-up email | Follow-up email |
+| 2nd | Phone the account manager within 4h | Phone next business day | Phone next business day |
+| 3rd | Escalate to production lead + contingency research | Source a backup vendor | Source a backup vendor |
+
+**On show day: skip email entirely. Phone or in-person only.** Never send a follow-up email on T-0.
+
+### Drafting rules for vendor follow-ups
+
+- Reference the **specific** original request or deliverable — not "following up on my last email".
+- State the deadline explicitly.
+- Ask for a **specific confirmation** ("Can you confirm delivery by 14 March?"), not an open question.
+- **No guilt, no pressure.** Vendors respond better to clarity than to escalation tone.
+- For a phone call, prepare: vendor name, account manager, the specific item, the deadline and why it matters, and the fallback question — *"If the original plan isn't possible, what's the alternative?"*
+
+### Budget and invoice context
+
+| Age | Status | Action |
+|---|---|---|
+| Within terms | Current | None |
+| 1–30 days | Nudge | Friendly reminder — assume oversight |
+| 31–60 days | Firm request | Direct ask with date and amount |
+| 60+ days | Escalation | Account lead; consider late fee or hold |
+
+Variance alerts: **Venue 5% over** (largest single line, small % = big dollars), **Catering 10%** (per-head counts fluctuate), **Marketing 15%** (most flexible), **Contingency 0% drawn before T-14** (should not be touched), **all others 10%**.
+
+---
+
+## 5. Production Coordination
+
+### 5.1 Pre-production
+
+**Site survey — non-negotiable for any first-time venue.** Record: power distribution and available amperage by area, network drops and their throughput, load-in vehicle access and dock dimensions, door widths for the largest scenic element, FOH position and sightlines, noise curfew, and rigging points with their load ratings. Route the technical read to `godmode-eventtech` — this skill records the findings and flags blockers, it does not validate the signal plan.
+
+**Paperwork gate.** Nothing loads in without: certificate of insurance (COI) from every vendor on site, venue access permits, and crew credentials. These are the most common cause of a T-1 access failure.
+
+**Run-of-show (ROS) is the single coordination artefact.** One document, versioned, owned by the production lead, distributed to every vendor. It defines: load-in window and sequence, soundcheck, doors, show start, each cue block, and load-out. A conflict discovered in the ROS is cheap. A conflict discovered at the dock is not.
+
+**Speaker materials — deadline framework:**
+
+| Milestone | Due | Deliverables |
+|---|---|---|
+| D-30 | Bio (25 / 50 / 100-word variants, third person) + headshot (min 300×300px) | |
+| D-21 | Session abstract (75 words, attendee-focused), learning outcomes, AV requirements | |
+| D-14 | Final slide deck, event template applied | |
+| D-7 | Travel, hotel, ground transport, dietary and accessibility requirements | |
+| D-1 | Attendance and schedule confirmed | |
+
+Learning outcomes use action verbs only — **implement, apply, build, create, deploy, evaluate, identify, master**. Never: *explore, discuss, learn about, understand, discover, dive into, unpack*.
+
+Banned in any bio or session description: *thought leader, visionary, guru, passionate about, world-class, cutting-edge, revolutionary, groundbreaking, leverage, synergize, transformative, innovative*. Replace with specific numbers, named clients, measurable outcomes, concrete credentials.
+
+### 5.2 Day-of flow
+
+| Phase | Anchor | What must be true to advance |
+|---|---|---|
+| **Load-in** | T-1 or earlier | COI and permits verified per vendor, power patched and tested, ROS sequence confirmed with the dock |
+| **Soundcheck** | Fixed slot, never "when ready" | Line check done, cue stack loaded, FOH and monitors positioned, walk-through with the client if contracted |
+| **Doors** | Published start | House open, accessibility routes clear, front-of-house briefed on the ROS |
+| **Show** | Per cue block | Production lead confirms each block against the ROS; deviations logged, not improvised |
+| **Strike** | After clearance | Equipment accounted for against the load-in manifest, rentals checked out before the truck leaves |
+
+**The strike manifest is the load-in manifest.** Count on the way in, count on the way out. Rentals left on site are invoiced at loss.
+
+### 5.3 Post-show wrap
+
+Within 72 hours of strike:
+
+- **Debrief** — what worked, what did not, what nearly failed. Blameless, specific, and it feeds the next ROS.
+- **Invoice triggers** — headcount actuals vs. quoted, rental shortfalls, overtime hours, damage claims. Capture while the evidence exists.
+- **Thank-you and forward look** — personalised, referencing what the attendee actually did, not a broadcast.
+- **Asset archiving** — recorded content, photography, final ROS, run sheets, and the vendor contact list with performance notes, filed where the next production can find them.
+- **Vendor performance note per vendor** — this is the input to §4's escalation tiers for the next event. A vendor who delivered three times running is not escalated on the first silence.
+
+### 5.4 Post-event reporting
+
+Performance tiers: **Exceeded** (beat goal by 10%+ on primary metrics), **Met** (within 10%), **Missed** (more than 10% below on one or more), **Mixed** (hit some, missed others — say which and why).
+
+Report structure: performance summary → what worked (with evidence) → what did not (with likely cause) → key insights (each tied to a data point) → specific recommendations for the next event → sponsor ROI if applicable.
+
+Channel attribution is **inherently imperfect** — most attendees meet several touchpoints before registering. Report it honestly, acknowledge mixed sources, and never over-credit a single channel.
+
+---
+
+## 6. Verification
+
+- [ ] Every event is classified into a phase (Normal / Planning / Advance / Load-In / Show Day) and that classification is stated, not assumed.
+- [ ] Urgency thresholds are applied relative to event proximity, not absolute days.
+- [ ] Every BLOCKED item names our team as owner — no BLOCKED item is left attributed to a vendor.
+- [ ] Technical execution questions were routed to `godmode-eventtech` / `bdbmediastorm` rather than answered from this skill.
+- [ ] No signal-flow, protocol, hardware-limit, or cue-execution instruction was issued from this skill.
+- [ ] COI, permits, and crew credentials are confirmed before load-in, per vendor.
+- [ ] The run-of-show is versioned, distributed, and owned by the production lead.
+- [ ] Speaker materials are checked against the D-30 / D-21 / D-14 / D-7 / D-1 framework.
+- [ ] Banned fluff words are absent from every bio, abstract, and session description.
+- [ ] On show day, no vendor follow-up was sent by email.
+- [ ] The strike manifest reconciles against the load-in manifest.
+- [ ] Invoice triggers captured within 72 hours of strike.
+- [ ] Attribution figures are presented with their acknowledged uncertainty.
+- [ ] No upstream script, Python file, or Composio tool dependency was added.