# workspace-governance

Adopt this skill: https://proskills.md/skills/other/samuellessa-afk-openclaw-skill-workspace-governance

Page: https://proskills.md/skills/other/samuellessa-afk-openclaw-skill-workspace-governance
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: SKILL.md
size: 8354
upstream: https://github.com/samuellessa-afk/openclaw-skill-workspace-governance/blob/HEAD/SKILL.md

````text
---
name: workspace-governance
description: "Governanca do workspace Clara Staff. Use ao criar, editar, mover ou organizar qualquer documento. Define estrutura de pastas, frontmatter, tags, convencoes de nomes e formato de arquivo. Garante compatibilidade com Obsidian e ChromaDB RAG."
version: 1.1.0
tags: [governance, workspace, writing]
metadata:
  openclaw:
    triggers:
      - criar arquivo
      - novo documento
      - onde salvar
      - organizar
      - mover arquivo
      - escrever nota
      - frontmatter
      - tags
---

# Workspace Governance — Clara Staff v1.1.0

Regras de governanca para escrita e organizacao de arquivos no workspace. Compativel com Obsidian (humano) e ChromaDB (RAG agentes).

**Glossario rapido:** RAG = Retrieval-Augmented Generation (busca semantica + LLM). ChromaDB = banco vetorial que indexa documentos para busca por similaridade. Embeddings = representacao numerica do texto que permite busca semantica. Wikilinks = `[[links]]` que conectam notas no Obsidian.

---

## 1. Estrutura de Pastas

```
workspace/
├── Pendencias.md                <- TODOs abertos (bootstrap)
├── Tarefas.md                   <- Tarefas com prazo (bootstrap)
├── MEMORY.md                    <- Memoria curada (~100 linhas max)
├── memory/                      <- Tier 2: logs diarios (auto hoje+ontem)
│   └── YYYY-MM-DD.md
├── knowledge/                   <- Tier 3: deep knowledge por dominio
│   ├── aprendizados/            <- Licoes por dominio
│   ├── bracha-capital/          <- Empresa, pipeline content, leads
│   ├── banco-canonico/          <- Prompts e regras canonicas
│   ├── backups/                 <- Backups de configs
│   ├── blogs/                   <- Blogs AI monitorados
│   ├── briefings/               <- Briefings historicos
│   ├── comunidade/              <- Discord/Telegram digests
│   ├── identidade/              <- Guia imagens, persona visual
│   ├── infra/                   <- Credenciais, emergencias, SSH
│   ├── instagram/               <- Cookies, monitoramento
│   ├── juridico/                <- Processos, jurisprudencia
│   ├── newsletters/             <- Newsletters assinadas
│   ├── para-claude-code/        <- Canal Clara -> CC
│   ├── planos/                  <- Auto-melhoria, estrategia
│   ├── receita/                 <- Plano mestre, leads, scorecard
│   └── sessoes/                 <- Historico de sessoes
├── projects/                    <- Projetos ativos
│   ├── bracha-os/
│   ├── bracha-mining/
│   └── bracha-capital/
├── curadoria/                   <- Pipeline de conteudo
│   ├── pendentes/
│   └── processados/
├── skills/                      <- Skills da Clara
└── vault-sync/                  <- BRACHA OS vault (read-only)
```

### Onde colocar cada arquivo (decision tree)

```
Novo arquivo?
├── TODO ou pendencia ativa? -> Pendencias.md (root)
├── Tarefa com prazo? -> Tarefas.md (root)
├── Insight duravel (<100 linhas total)? -> MEMORY.md
├── Log do dia? -> memory/YYYY-MM-DD.md
├── Licao aprendida? -> knowledge/aprendizados/
├── Pipeline content (LinkedIn, blog)? -> knowledge/bracha-capital/
├── Lead, scorecard, ebook? -> knowledge/receita/
├── Processo judicial? -> knowledge/juridico/
├── Credencial, SSH, emergency? -> knowledge/infra/
├── Discord/Telegram digest? -> knowledge/comunidade/
├── Blog AI monitorado? -> knowledge/blogs/
├── Newsletter? -> knowledge/newsletters/
├── Briefing historico? -> knowledge/briefings/
├── Mensagem para Claude Code? -> knowledge/para-claude-code/
├── Plano estrategico? -> knowledge/planos/
├── Backup de config? -> knowledge/backups/
├── Projeto ativo? -> projects/<nome>/
├── Item de curadoria? -> curadoria/pendentes/ ou processados/
├── Consulta ao BRACHA OS? -> vault-sync/ (READ-ONLY, nunca escrever)
└── Nao sei -> knowledge/ (pasta mais proxima do tema)
```

---

## 2. Convencoes de Nomes

1. **kebab-case sempre:** `parecer-recurso-caso-xyz.md`, nunca `Parecer Recurso.md`
2. **Max ~50 caracteres** no nome (sem extensao)
3. **Sem versao no nome** — versao no frontmatter
4. **Datas no nome quando temporal:** `2026-03-24-discord-digest.md`
5. **Sem espacos, sem maiusculas, sem caracteres especiais**
6. **Pastas novas:** kebab-case, so criar dentro de `knowledge/` ou `projects/`

---

## 3. Frontmatter Obrigatorio

Todo arquivo no workspace (exceto bootstrap files e memory/) DEVE ter frontmatter YAML.

### Campos obrigatorios

```yaml
---
type: <tipo>                     # Ver taxonomia abaixo
status: active                   # active | draft | deprecated | archived
tags:                            # Min 1 dominio + 1 tipo (ver Secao 4)
  - dom-juridico
  - tipo-analise
domain: legal                    # ChromaDB collection (ver lista abaixo)
summary: "Sujeito + verbo + contexto. Max 100 palavras."
created: 2026-03-24              # YYYY-MM-DD
updated: 2026-03-24              # YYYY-MM-DD
---
```

### Campos condicionais (quando aplicavel)

```yaml
---
author: clara-staff              # Quem criou (default: clara-staff)
priority: alto                   # critico | alto | medio | baixo
related_to: [plano-mestre, scorecard]  # Grafo de conhecimento
consumers: ["[[clara-staff]]"]   # Quem deve ler (wikilinks, futuro multi-agent)
visibility: public               # public | agent-only | restricted
version: "1.0.0"                 # SemVer para docs versionados
aliases:                         # Nomes alternativos para busca
  - scorecard receita
---
```

### Document Types (`type`)

| type | Para que | Onde |
|------|----------|------|
| `briefing` | Resumo executivo, TL;DR | knowledge/briefings/, memory/ |
| `report` | Relatorio, digest, resumo periodico | knowledge/comunidade/, knowledge/blogs/ |
| `analysis` | Analise, avaliacao, pesquisa | knowledge/ (qualquer) |
| `plan` | Plano, estrategia, roadmap | knowledge/planos/, knowledge/receita/ |
| `reference` | Material de referencia, lookup | knowledge/infra/, knowledge/banco-canonico/ |
| `lead` | Lead, prospect, contato | knowledge/receita/leads/ |
| `legal` | Documento juridico, peticao, acordao | knowledge/juridico/ |
| `decision` | Decisao tomada, questao resolvida | knowledge/ (qualquer) |
| `template` | Template reutilizavel | knowledge/bracha-capital/templates/ |
| `learning` | Retro, licao aprendida | knowledge/aprendizados/ |
| `asset` | Entregavel publicado (ebook, post) | knowledge/bracha-capital/, projects/ |
| `draft` | Rascunho em progresso | knowledge/ (qualquer) |
| `data` | Dados brutos, dataset, export | knowledge/ (qualquer) |
| `task` | Acao pendente, lembrete | root (Pendencias.md, Tarefas.md) |
| `log` | Log diario, sessao | memory/, knowledge/sessoes/ |
| `digest` | Compilado periodico | knowledge/comunidade/, knowledge/newsletters/ |
| `pipeline` | Pipeline de vendas/conteudo | knowledge/bracha-capital/, knowledge/receita/ |

### Tabela Mestra de Dominios (pasta + domain + tag DEVEM estar alinhados)

Um arquivo em `knowledge/juridico/` **DEVE** ter `domain: legal` e tag `dom-juridico`. Nunca misturar.

| Pasta (`knowledge/`) | `domain` (ChromaDB) | Tag (`dom-`) | Collection |
|----------------------|--------------------|--------------|-----------|
| `juridico/` | `legal` | `dom-juridico` | clara-legal |
| `receita/` | `revenue` | `dom-receita` | clara-revenue |
| `bracha-capital/` | `corporate` | `dom-corporativo` | clara-corporate |
| `infra/` | `infra` | `dom-infra` | clara-infra |
| `comunidade/` | `community` | `dom-comunidade` | clara-community |
| `blogs/`, `newsletters/` | `research` | `dom-pesquisa` | clara-research |
| `aprendizados/` | `learning` | `dom-aprendizado` | clara-learning |
| `briefings/` | `personal` | `dom-pessoal` | clara-personal |
| `planos/` | `learning` | `dom-aprendizado` | clara-learning |
| `identidade/`, `backups/` | `infra` | `dom-infra` | clara-infra |
| `instagram/` | `content` | `dom-conteudo` | clara-content |
| `para-claude-code/` | `infra` | `dom-infra` | clara-infra |
| `sessoes/` | `learning` | `dom-aprendizado` | clara-learning |
| (projects/) | `corpor
````

## File: README.md
upstream: https://github.com/samuellessa-afk/openclaw-skill-workspace-governance/blob/HEAD/README.md

````text
# workspace-governance

OpenClaw skill for workspace file governance. Teaches your AI agent how to organize files, write consistent frontmatter, use standardized tags, and follow naming conventions.

Designed for compatibility with **Obsidian** (human navigation) and **ChromaDB RAG** (agent retrieval).

## What it does

- **Folder structure** with decision tree ("where does this file go?")
- **Frontmatter standard** compatible with ChromaDB vector search (17 document types, 10 domains)
- **Tag taxonomy** with 35 tags in 4 axes: domain, type, lifecycle, priority
- **Naming conventions** (kebab-case, max 50 chars, date prefixes)
- **Writing format** optimized for RAG chunking (atomic notes, wikilinks, callouts)
- **Memory tiers** (Tier 1: always loaded, Tier 2: daily logs, Tier 3: deep knowledge)
- **Exception handling** (multi-domain files, large documents, binary files, orphans)
- **Multi-agent ready** (authorship, conflict resolution, inter-agent communication)
- **Self-governance** (SemVer, RFC process, periodic review, anti-patterns)

## Quality

Audited via CANN (Ciclo de Auditoria Nao-Negociavel) with 3 LLMs:

| Auditor | Score |
|---------|-------|
| GPT-4.1 | 9.8/10 |
| Gemini 2.5 Pro | 9.6/10 |
| Grok 3 | 9.0/10 |
| **Average** | **9.47/10** |

## Install

Copy the `SKILL.md` file to your OpenClaw workspace skills directory:

```bash
mkdir -p ~/.openclaw/workspace/skills/workspace-governance
cp SKILL.md ~/.openclaw/workspace/skills/workspace-governance/
```

Or clone this repo:

```bash
cd ~/.openclaw/workspace/skills
git clone https://github.com/samuellessa-afk/openclaw-skill-workspace-governance.git workspace-governance
```

The skill loads automatically when triggers match (creating files, organizing, frontmatter, tags).

## Customize

The skill is designed to be adapted. Key sections to customize for your use case:

1. **Folder structure** (Section 1) — adjust to your workspace layout
2. **Domain table** (Section 3) — map your domains to ChromaDB collections
3. **Tag taxonomy** (Section 4) — add/remove tags for your domain
4. **Memory tiers** (Section 6) — adjust based on your memory backend

## Files

| File | Purpose |
|------|---------|
| `SKILL.md` | The skill itself (install this) |
| `CHANGELOG.md` | Version history |
| `BACKLOG.md` | Planned improvements |

## Built by

[Bracha Capital](https://bracha.capital) — AI-first M&A boutique from Belo Horizonte, Brazil.

Part of the [BRACHA OS](https://github.com/samuellessa-afk) ecosystem.

## License

MIT
````
