Back to corpus
research noteexperiment writeup candidatescore 32

Pulse v2 — Governance-Aware Autonomous Development

Pulse v2 enhances autonomous development sessions with: - **Governance Integration** — Reads and updates project checklists - **Skill Loading** — References relevant SKILL.md files - **Context Injection** — Pulls memories from Orbit/MCP - **Conventional Commits** — Standardized commit messages - **Pattern Compliance** — Matches existing code style

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

--- name: pulse-v2 description: Governance-aware autonomous development sessions with skill integration, checklist tracking, and conventional commits homepage: https://github.com/clawdbot/clawdbot user-invocable: true command-dispatch: pulsev2 metadata.clawdbot: {"governance": true, "mcp_aware": true} --- Pulse v2 enhances autonomous development sessions with: - **Governance Integration** — Reads and updates project checklists - **Skill Loading** — References relevant SKILL.md files - **Context Injection** — Pulls memories from Orbit/MCP - **Conventional Commits** — Standardized commit messages - **Pattern Compliance** — Matches existing code style This automatically: 1. Reads `.governance/` files 2. Loads relevant skills 3. Runs the task 4. Updates checklist on completion 5. Commits with conventional format | Task Type | Skills to Load | |-----------|----------------| | iOS/Swift game | `gam:mfp`, `governance-framework` | | Expo/React Native | `expo-mobile`, `expo-preview` | | AI features | `nano-banana-pro`, `gemini` | | Testing | `coding-agent` | | Video/Media | `vid:remotion`, `video-frames` | | Creative | `tie`, `art:creative`, `spf` | | Aspect | v1 | v2 | |--------|----|----| | Governance | ❌ Ignored | ✅ Read & updated | | Skills | ❌ Not loaded | ✅ Referenced | | Memory | ❌ Isolated | ✅ Context injected | | Commits | Generic | Conventional format | | Documentation | Optional | Required | | Tracking | Manual | Auto-updated | | Code style | Random | Pattern-matched |

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.