Skip to content

Releases

v0.2.0 — Safer graduation, clearer public workflow

Choose a tag to compare

@iBlinkQ iBlinkQ released this 28 Jul 16:17

Turn project work into reusable knowledge.

Project Cairn v0.2.0 is the first substantial update after the initial public release. It keeps the documentation-first architecture while making the Skill easier to understand, safer to operate, and cheaper to load in context.

Highlights

  • Progressive disclosure for graduation providers. The shared graduation workflow now loads separately from the Lark, Notion, and Obsidian execution paths. Candidate assessment uses 41.8% less selected graduation context; the largest single-provider path uses 22.5% less.
  • A stricter write gate. Provider-side writes require the selected provider reference to be read and that provider's read-only preflight to return status: ok; a dry-run does not substitute for the gate.
  • Human provenance and origin quotes. Project and knowledge-base notes can preserve contributors, human confirmers, and short attributed quotes while keeping sensitive material out.
  • Safe re-graduation. Obsidian, Lark, and Notion adapters update the same destination object and union provenance instead of creating duplicates.
  • Instance upgrade guidance. skill_spec_date, references/upgrade.md, and audit checks make drift in previously initialized projects visible without background update hooks.
  • Deferred provider setup. A project can start with graduation.provider: none and connect Obsidian, Notion, or Lark only when the first real graduation is ready.
  • A clearer public entry point. The bilingual README, diagrams, WorkBuddy installation path, and interactive GitHub Pages guide now explain the workflow before implementation details.

Verification

  • 9/9 fixture scenarios passed their deterministic red-to-green checks.
  • Provider update and provenance regression suites passed for Obsidian, Lark, and Notion.
  • Recursive reference routing, anchor, live-link, and character-budget checks passed.
  • Shell syntax, Python compilation, Skill metadata validation, public asset checks, and sensitive-material scans passed.

Upgrade notes

The graduation reference split does not require changes to initialized projects or graduated notes. Existing projects can use the audit and upgrade flow in references/upgrade.md to detect earlier spec drift. Project Cairn remains documentation-first: no CLI daemon, background hook, silent provider write, or automatic migration was added.

v0.1.0 — First public release

Choose a tag to compare

@iBlinkQ iBlinkQ released this 03 Jul 13:52

Turn project work into reusable knowledge.

Project Cairn is an AI-agent skill for Claude Code, Codex, and compatible agents. It turns what an AI-collaboration project did — decisions, dead ends, solved pitfalls, validated approaches — into reusable knowledge that travels to the next project instead of dying with the session.

This is the first public release: documentation-first, v0.1. Instructions, templates, and provider adapter scripts only — no CLI, MCP server, or background hook to install.

What's in it

  • Two-layer model — project-side AGENTS.md + cairn/ (rules, state, local conclusions) and a knowledge-base layer (cross-project, reusable domain knowledge), connected by one-directional graduation: knowledge moves project → knowledge base at the moment it's validated as reusable, never silently back.
  • Three verified graduation providers, each adapted to how the platform actually works rather than forced into one generic shape: Obsidian (vault-relative files + INDEX.md, native WikiLinks), Lark/Feishu wiki (native resource API, wiki:wiki scope), Notion (direct REST, database-as-container-and-index).
  • Trigger-based creation — a new project only needs AGENTS.md. Topic notes, ROADMAP.md, Reference/, Cited.md are created only when a real signal shows up, not pre-built as empty shells.
  • User-level cascading config — save your usual provider targets, git policy, and language once; every later cairn init offers a one-key reuse instead of re-asking.
  • Branch-closure review — before an exploration branch is merged, abandoned, or rolled back, a lightweight review salvages anything worth keeping.
  • Audit — checks for drift, contradictions, missing graduation back-pointers, and engineering assets that leaked into the knowledge layer.

Install

git clone https://github.com/iBlinkQ/project-cairn.git ~/.claude/skills/project-cairn   # Claude Code
git clone https://github.com/iBlinkQ/project-cairn.git ~/.agents/skills/project-cairn   # Codex

See README.md (also available in Chinese) for the full quick start and docs map.

License

MIT