invos 1.0.0

package/README.md

@@ -0,0 +1,39 @@
+# invos
+
+CLI do **INVOS** — sistema de memória multi-agente em arquivos (prioridade, clientes, proposta, conteúdo).
+
+## Install
+
+```bash
+npx invos@latest init meu-negocio
+# ou
+npm i -g invos
+invos init meu-negocio
+```
+
+## Commands
+
+| Command | What it does |
+|---------|----------------|
+| `invos init [dir]` | Cria pasta nova com o kit |
+| `invos install` | Injeta INVOS no diretório atual (repo existente) |
+| `invos update` | Atualiza skills/sistema; **não** mexe em `memoria/` / clientes reais |
+| `invos doctor` | Valida instalação |
+
+## After init
+
+```bash
+cd meu-negocio
+# Abra no Claude / Cursor / Codex / Grok
+# Diga: Segue o COMECE-AQUI
+```
+
+## Env (opcional)
+
+| Var | Uso |
+|-----|-----|
+| `INVOS_KIT_PATH` | Override do kit (dev / kit custom) |
+
+## Site
+
+https://inovadigitalid.com/invos

package/bin/invos.js

@@ -0,0 +1,78 @@
+#!/usr/bin/env node
+import { readFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+import { dirname, resolve } from 'node:path';
+import { init } from '../src/commands/init.js';
+import { install } from '../src/commands/install.js';
+import { update } from '../src/commands/update.js';
+import { doctor } from '../src/commands/doctor.js';
+import { loadManifest } from '../src/manifest.js';
+import { resolveKitRoot } from '../src/resolve-kit.js';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+
+const cmd = process.argv[2];
+const args = process.argv.slice(3);
+
+function extractDir(args) {
+  const idx = args.indexOf('--dir');
+  if (idx !== -1 && args[idx + 1]) {
+    const dir = resolve(process.cwd(), args[idx + 1]);
+    args.splice(idx, 2);
+    return dir;
+  }
+  return null;
+}
+
+function help() {
+  console.log(`
+INVOS CLI — npx invos <command>
+
+Commands:
+  init [dir]           Create new INVOS project from scratch
+  install [--dir <p>]  Install INVOS into dir (default: cwd)
+  update [--dir <p>]   Update shipped files, preserve user data
+  doctor [--dir <p>]   Validate installation
+
+Options:
+  --help               Show this help
+  --version            Show version
+`);
+}
+
+async function main() {
+  if (!cmd || cmd === '--help' || cmd === '-h') { help(); return; }
+  if (cmd === '--version' || cmd === '-v') {
+    const pkg = JSON.parse(readFileSync(resolve(__dirname, '../package.json'), 'utf-8'));
+    console.log(pkg.version);
+    return;
+  }
+
+  const KIT_ROOT = resolveKitRoot();
+  const kit = loadManifest(resolve(KIT_ROOT, 'INVOS.json'));
+  if (!kit) {
+    console.error('INVOS.json not found at', KIT_ROOT);
+    process.exit(1);
+  }
+
+  switch (cmd) {
+    case 'init':
+      await init(kit, KIT_ROOT, args);
+      break;
+    case 'install':
+      await install(kit, KIT_ROOT, extractDir(args) || process.cwd(), args);
+      break;
+    case 'update':
+      await update(kit, KIT_ROOT, extractDir(args) || process.cwd(), args);
+      break;
+    case 'doctor':
+      await doctor(kit, KIT_ROOT, extractDir(args) || process.cwd(), args);
+      break;
+    default:
+      console.error('Unknown command:', cmd);
+      help();
+      process.exit(1);
+  }
+}
+
+main().catch(err => { console.error(err.message); process.exit(1); });

package/kit/.agents/skills/apple/DESCRIPTION.md

@@ -0,0 +1,2 @@
+Apple / macOS skills — tools that interact with the Mac desktop (Finder,
+native apps) or system features (accessibility, screenshots).

package/kit/.agents/skills/apple/apple-notes/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: apple-notes
+description: "Manage Apple Notes via memo CLI: create, search, edit."
+version: 1.0.0
+author: Hermes Agent
+license: MIT
+platforms: [macos]
+metadata:
+  hermes:
+    tags: [Notes, Apple, macOS, note-taking]
+    related_skills: [obsidian]
+prerequisites:
+  commands: [memo]
+---
+
+# Apple Notes
+
+Use `memo` to manage Apple Notes directly from the terminal. Notes sync across all Apple devices via iCloud.
+
+## Prerequisites
+
+- **macOS** with Notes.app
+- Install: `brew tap antoniorodr/memo && brew install antoniorodr/memo/memo`
+- Grant Automation access to Notes.app when prompted (System Settings → Privacy → Automation)
+
+## When to Use
+
+- User asks to create, view, or search Apple Notes
+- Saving information to Notes.app for cross-device access
+- Organizing notes into folders
+- Exporting notes to Markdown/HTML
+
+## When NOT to Use
+
+- Obsidian vault management → use the `obsidian` skill
+- Bear Notes → separate app (not supported here)
+- Quick agent-only notes → use the `memory` tool instead
+
+## Quick Reference
+
+### View Notes
+
+```bash
+memo notes                        # List all notes
+memo notes -f "Folder Name"       # Filter by folder
+memo notes -s "query"             # Search notes (fuzzy)
+```
+
+### Create Notes
+
+```bash
+memo notes -a                     # Interactive editor
+memo notes -a "Note Title"        # Quick add with title
+```
+
+### Edit Notes
+
+```bash
+memo notes -e                     # Interactive selection to edit
+```
+
+### Delete Notes
+
+```bash
+memo notes -d                     # Interactive selection to delete
+```
+
+### Move Notes
+
+```bash
+memo notes -m                     # Move note to folder (interactive)
+```
+
+### Export Notes
+
+```bash
+memo notes -ex                    # Export to HTML/Markdown
+```
+
+## Limitations
+
+- Cannot edit notes containing images or attachments
+- Interactive prompts require terminal access (use pty=true if needed)
+- macOS only — requires Apple Notes.app
+
+## Rules
+
+1. Prefer Apple Notes when user wants cross-device sync (iPhone/iPad/Mac)
+2. Use the `memory` tool for agent-internal notes that don't need to sync
+3. Use the `obsidian` skill for Markdown-native knowledge management

package/kit/.agents/skills/apple/apple-reminders/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: apple-reminders
+description: "Apple Reminders via remindctl: add, list, complete."
+version: 1.0.0
+author: Hermes Agent
+license: MIT
+platforms: [macos]
+metadata:
+  hermes:
+    tags: [Reminders, tasks, todo, macOS, Apple]
+prerequisites:
+  commands: [remindctl]
+---
+
+# Apple Reminders
+
+Use `remindctl` to manage Apple Reminders directly from the terminal. Tasks sync across all Apple devices via iCloud.
+
+## Prerequisites
+
+- **macOS** with Reminders.app
+- Install: `brew install steipete/tap/remindctl`
+- Grant Reminders permission when prompted
+- Check: `remindctl status` / Request: `remindctl authorize`
+
+## When to Use
+
+- User mentions "reminder" or "Reminders app"
+- Creating personal to-dos with due dates that sync to iOS
+- Managing Apple Reminders lists
+- User wants tasks to appear on their iPhone/iPad
+
+## When NOT to Use
+
+- Scheduling agent alerts → use the cronjob tool instead
+- Calendar events → use Apple Calendar or Google Calendar
+- Project task management → use GitHub Issues, Notion, etc.
+- If user says "remind me" but means an agent alert → clarify first
+
+## Quick Reference
+
+### View Reminders
+
+```bash
+remindctl                    # Today's reminders
+remindctl today              # Today
+remindctl tomorrow           # Tomorrow
+remindctl week               # This week
+remindctl overdue            # Past due
+remindctl all                # Everything
+remindctl 2026-01-04         # Specific date
+```
+
+### Manage Lists
+
+```bash
+remindctl list               # List all lists
+remindctl list Work          # Show specific list
+remindctl list Projects --create    # Create list
+remindctl list Work --delete        # Delete list
+```
+
+### Create Reminders
+
+```bash
+remindctl add "Buy milk"
+remindctl add --title "Call mom" --list Personal --due tomorrow
+remindctl add --title "Meeting prep" --due "2026-02-15 09:00"
+```
+
+### Due Time vs Alarm / Early Nudge
+
+`--due` and `--alarm` are different fields:
+
+- `--due` sets the reminder's due date/time.
+- `--alarm` sets the EventKit alarm/notification trigger. Timed due reminders may default to an alarm at the due time, but pass `--alarm` explicitly when the user asks for an earlier nudge.
+
+For a reminder due at 2:00 PM with a notification 30 minutes earlier:
+
+```bash
+remindctl add --title "Hairdresser" --due "2026-05-15 14:00" --alarm "2026-05-15 13:30"
+```
+
+To edit an existing reminder:
+
+```bash
+remindctl edit 87354 --due "2026-05-15 14:00" --alarm "2026-05-15 13:30"
+```
+
+The Reminders UI may show or group the item by the alarm time because that is when the notification fires. Verify with JSON instead of assuming the due time moved:
+
+```bash
+remindctl today --json
+```
+
+Expected shape:
+
+- `dueDate`: actual due time
+- `alarmDate`: notification / early nudge time
+
+Apple's public `EKReminder` docs list only reminder-specific properties. Alarm support comes from inherited `EKCalendarItem` behavior exposed by remindctl's `--alarm` flag.
+
+### Complete / Delete
+
+```bash
+remindctl complete 1 2 3          # Complete by ID
+remindctl delete 4A83 --force     # Delete by ID
+```
+
+### Output Formats
+
+```bash
+remindctl today --json       # JSON for scripting
+remindctl today --plain      # TSV format
+remindctl today --quiet      # Counts only
+```
+
+## Date Formats
+
+Accepted by `--due` and date filters:
+- `today`, `tomorrow`, `yesterday`
+- `YYYY-MM-DD`
+- `YYYY-MM-DD HH:mm`
+- ISO 8601 (`2026-01-04T12:34:56Z`)
+
+## Rules
+
+1. When user says "remind me", clarify: Apple Reminders (syncs to phone) vs agent cronjob alert
+2. Always confirm reminder content and due date before creating
+3. Use `--json` for programmatic parsing

package/kit/.agents/skills/audit/SKILL.md

@@ -0,0 +1,177 @@
+---
+name: audit
+description: Use for AIOS audit — scores project against Four Cs, surfaces leverage-weighted top-3 gaps. Read-only. Run on Day 7, then weekly. Watch score climb.
+---
+
+## What this skill does
+
+Runs the **Four Cs Audit** on the current project. Reads (never writes) the project's operating manual, memory, skills, agents, connections, decisions, and references. Scores each of the Four Cs out of 25. Surfaces strengths and the top 3 leverage-weighted gaps with concrete next-step commands.
+
+**Scope is structural — "is the AIOS built right?"** It is NOT a capability planner. Capability gaps belong to `/level-up`.
+
+First run is the baseline. Re-run weekly to watch the score climb.
+
+## Today's context
+
+- **Date:** `date +%Y-%m-%d`
+- **Project root:** the current working directory
+
+## The Four Cs (scored 25 each = 100 total)
+
+| Layer | Test |
+|---|---|
+| **Context** | Knows the business — identity, team, voice, decisions, references |
+| **Connections** | Reaches the user's stuff — MCPs, integrations, data sources |
+| **Capabilities** | Knows how to do work — skills + agents |
+| **Cadence** | Runs without being asked — schedules, hooks, recurring rituals |
+
+## Execution
+
+### Step 1: Discover the project shape
+
+The audit looks for **patterns and intent**, not exact paths. Use Glob and Read to check:
+
+**Operating manual:** `CLAUDE.md` (root), `CLAUDE.local.md` (gitignored).
+**Memory:** `memoria/` folder.
+**Skills:** `.agents/skills/*/SKILL.md` — count + frontmatter. Also check `.claude/skills/*/SKILL.md` (mirror surface).
+**Agents:** `.claude/agents/*.md` — count + frontmatter.
+**Connection mechanisms** (any of these = reachable):
+- MCPs: `opencode.json` (mcpServers key), `.claude/settings.local.json` (mcpServers key), `.mcp.json` (root or subproject)
+- API scripts: `scripts/*.py|.js|.ts` documented in CLAUDE.md
+- Export pipelines: `data/`, `imports/`, `saidas/` with refresh script + last-run timestamp
+- API keys + reference guide: `.env` entries + corresponding `references/{tool}-api.md`
+- Vercel functions: `api/` directory
+
+**Connections registry:** `connections.md` (root).
+**Reference guides:** `references/` folder.
+**Decisions:** `decisions/log.md` (root).
+**SOPs:** `docs/` folder.
+**Templates:** `conhecimento/templates/`, `templates/`.
+**Hooks / scheduled jobs:** `.claude/hooks/` for session hooks; `.github/workflows/` for CI schedules.
+
+Don't penalize for non-canonical names if equivalent intent is captured elsewhere.
+
+### Step 2: Score each C (25 points each)
+
+#### Context (25 pts)
+
+| Criterion | Points | How to detect |
+|---|---|---|
+| Operating manual exists and is substantive (>200 words) | 5 | Read CLAUDE.md, count words |
+| Identity / role / voice captured | 5 | CLAUDE.md mentions who the user is + role/mission, OR `memoria/perfil.md` exists |
+| Persistent memory exists with multiple entries | 5 | `memoria/` has >3 files |
+| Reference docs exist | 5 | `references/`, `docs/`, or `conhecimento/voice/` has >=1 file |
+| Decisions captured | 5 | `decisions/log.md` or equivalent has >=1 entry |
+
+#### Connections (25 pts) — domain-aware, mechanism-agnostic
+
+A "reachable" connection counts via ANY mechanism: MCP, script, export pipeline, or `.env` key + `references/{tool}-api.md`.
+
+**The 7 Tier-1 Universal Data Domains:**
+
+| # | Domain | Examples |
+|---|---|---|
+| 1 | Revenue / Financials | Stripe, Skool, GoHighLevel, QuickBooks, Looker |
+| 2 | Customer interactions | HubSpot, Salesforce, Gmail-as-CRM, Skool DMs |
+| 3 | Calendar | Google Cal, Outlook, Calendly |
+| 4 | Communication | Gmail, Outlook, Slack, Teams, Telegram, Discord |
+| 5 | Project / task tracking | ClickUp, Asana, Linear, Notion DB, GitHub Issues |
+| 6 | Meeting intelligence | Granola, Otter, Fireflies, Gong, Zoom |
+| 7 | Knowledge / files | Notion, Drive, Dropbox, Confluence, GitHub repo |
+
+**Tier-2 (bonus):** AI service API keys, decisions/history, content/publishing.
+
+| Criterion | Points | How to detect |
+|---|---|---|
+| Tier-1 domain coverage | 10 | 1.4 pts per tier-1 domain reachable. Round to nearest 0.5. Cap 10. |
+| Reference guide presence | 5 | -1 per connected tool with no `references/{tool}-api.md`. Floor 0. |
+| Auth / pipeline freshness | 5 | -1 per connection in needs-auth/expired state, or script with no run within 30 days. Floor 0. |
+| Documentation in `connections.md` | 3 | 0 if missing; 1 sparse; 2 most; 3 covers all reachable. |
+| Read-AND-write balance | 2 | At least one connection can WRITE. 0 if all read-only. |
+
+#### Capabilities (25 pts)
+
+| Criterion | Points | How to detect |
+|---|---|---|
+| 3+ skills installed | 10 | Count `.agents/skills/*/SKILL.md` >= 3 |
+| 1+ user-built skill | 10 | Skill names not in canonical list: `onboard`, `audit`, `level-up`, plus any shipped Anthropic skills |
+| 1+ agent defined | 5 | Count `.claude/agents/*.md` >= 1 |
+
+#### Cadence (25 pts)
+
+| Criterion | Points | How to detect |
+|---|---|---|
+| 1+ recurring/scheduled trigger | 10 | `.github/workflows/*.yml` with cron/schedule, OR hook scripts in `.claude/hooks/` |
+| Recent activity / usage signal | 10 | Skills modified within 30 days, OR `decisions/log.md` has entry within 30 days |
+| Templates folder populated | 5 | `templates/` or `.claude/templates/` has >=1 file |
+
+### Step 3: Identify top 3 gaps by leverage
+
+For each criterion that lost points: leverage = (points lost) × (impact multiplier).
+
+**Impact multipliers:**
+- 0 tier-1 domains reachable: **4x** (AIOS is blind to the business)
+- Operating manual missing or thin: **3x** (foundation)
+- <=2 tier-1 domains reachable: **3x** (Connections is the gateway to live data)
+- 0 skills: **2x** (no Capabilities = no AIOS)
+- No recurring trigger: **2x** (no Cadence = no autonomy)
+- All connections read-only: **2x** (viewer, not an OS)
+- 0 reference guides for connected tools: **1.5x**
+- No decisions log: **1.5x**
+- All others: **1x**
+
+Sort gaps by leverage descending. Take top 3. For each, write a one-line concrete next step.
+
+### Step 4: Output the report
+
+Print directly in chat (Markdown). Format:
+
+```
+# AIOS Audit — {date}
+**Score: {total}/100** ({stage})
+
+Stage thresholds:
+- 0-39 → Stage 0: Foundation
+- 40-69 → Stage 1: Built
+- 70-89 → Stage 2: Compounding
+- 90-100 → Stage 3: Autonomous
+
+## Scoreboard
+
+Context        {bar}  {n}/25  {label}
+Connections    {bar}  {n}/25  {label}
+Capabilities   {bar}  {n}/25  {label}
+Cadence        {bar}  {n}/25  {label}
+
+(bar = ## per 5pts; label = "Strong" >=20, "Solid" 15-19, "Thin" 8-14, "Missing" <8)
+
+## Strengths
+- {1-3 short bullets from highest-scoring criteria}
+
+## Top 3 Gaps (ranked by leverage)
+1. **{gap name}** (-{n}pts x {multiplier})
+   -> {concrete next-step}
+2. **{gap name}** (-{n}pts x {multiplier})
+   -> {concrete next-step}
+3. **{gap name}** (-{n}pts x {multiplier})
+   -> {concrete next-step}
+
+## Suggested next: {single most leveraged action}
+
+---
+Structural gaps only. To explore CAPABILITY gaps, run /level-up after this audit.
+```
+
+### Step 5: Offer to save the report
+
+After printing, ask: "Save this audit to `audits/audit-{date}.md` so you can track score over time?" If yes, write it. This is the only writable side effect.
+
+## Notes
+
+- **Read-only by default.** Never modify CLAUDE.md, memory, skills, or any project files. Only optional write is the audit report.
+- **Be flexible about file names.** Don't penalize for using non-canonical names if intent is captured.
+- **Be honest, not generous.** A 95/100 is rare. Most setups land 40-70.
+- **Speed matters.** Report in under 60 seconds wall-clock.
+- **Cadence detection is fuzzy.** Infer from workflows and hook scripts if cron data isn't cleanly available.
+
+> *Adapted from The Three Ms of AI™ © 2026 Nate Herk.*

package/kit/.agents/skills/design-marca/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: design-marca
+description: >-
+  Extrai ou atualiza a identidade visual do negócio em marca/marca.md (cores,
+  tipografia, assets). Use quando: "extrai a marca do meu site", "design system",
+  "/design", "atualiza cores da marca", "pega o branding do site X".
+---
+
+# Design → marca/ (INVOS)
+
+Adaptação da ideia **design-md** pro INVOS: o destino **não** é `DESIGN.md` na raiz.  
+Destino canônico = **`marca/marca.md`** (+ `marca/assets/` se houver logo).
+
+Objetivo: proposta HTML e qualquer saída usarem **as cores e a voz reais** do prestador.
+
+## Gatilhos
+
+- “Extrai a marca do site …”, “/design …”, “atualiza brand”, “minhas cores”
+- Onboard ofereceu preencher marca e o user mandou URL
+- Proposta pediu brand e `marca/marca.md` ainda é template
+
+## Fontes de dados (ordem)
+
+1. **URL do site do usuário** (preferido se tiver)  
+2. Respostas manuais (nome, cor favorita, tom)  
+3. Já existente em `marca/marca.md` / `memoria/empresa.md` (não apagar o que for bom)
+
+## Extração de site (se houver URL)
+
+Normalizar URL (`https://` se faltar).
+
+Tentar, nesta ordem:
+
+1. MCP/CLI Hyperbrowser se existir no ambiente:  
+   `hx web fetch <url> --format branding`  
+   ou tool `scrape_webpage` com branding  
+2. Se **não** houver Hyperbrowser / API key:  
+   - abrir a página com ferramenta de browse disponível, **ou**  
+   - perguntar 4 coisas manuais: cor principal (hex), cor de texto, fonte se souber, tom visual  
+   - **Não inventar** paleta “bonita” sem base
+
+**Regra:** só grave hex/fontes que foram **extraídos ou ditos pelo user**. Sem alucinar design system completo.
+
+## O que gravar
+
+### Sempre atualizar `marca/marca.md`
+
+Preencher / mesclar seções:
+
+- Identidade (nome da marca, site, contato se souber)  
+- Cores (primária, fundo, texto — hex)  
+- Tipografia (se veio na extração)  
+- Voz: se o user já tem tom em `empresa.md`, **copie** pra cá (não deixe só em empresa)
+
+Mantenha o formato do template. Não reescreva o arquivo apagando campos úteis sem necessidade.
+
+### Logo
+
+- Se o user **anexar** logo: salvar em `marca/assets/logo.png` ou `logo.svg` e marcar **Logo presente? sim**  
+- Se só URL de logo clara e download for possível/seguro: salvar em `assets/`  
+- Senão: deixar “não” e seguir só com cor + nome
+
+### Espelhar o mínimo em `memoria/empresa.md`
+
+Atualize a seção **Brand** (ou o ponteiro) pra não divergir:
+
+- Marca, Cor, Site, Contato = mesmos valores de `marca/marca.md`
+
+`marca/marca.md` continua sendo a **fonte**; empresa só resume.
+
+## Output no chat
+
+```
+✅ Marca atualizada em marca/marca.md
+- Primária: #…
+- Fundo / texto: …
+- Logo: sim (path) | não
+Próximo: gerar proposta ou post já usa essas cores.
+```
+
+## O que NÃO fazer
+
+- Salvar `DESIGN.md` na raiz do INVOS (confunde com o core)  
+- Inventar cores/fontes “de gosto”  
+- Misturar brand do **cliente** com a marca do prestador  
+- Depender de API paga sem fallback manual  
+
+## Relação com squad `brand`
+
+Squad brand = consultoria profunda (posicionamento, brand book).  
+Esta skill = **operacional**: 5 minutos, arquivo que a proposta lê.  
+Se o squad gerar brand book, **resuma** cores/voz/logo path em `marca/marca.md`.