Skip to content

v0.2.0

Choose a tag to compare

View all tags
@pserey pserey released this 30 Jul 00:29
v0.2.0
4b83243
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Second release of megabrain.md — the specification now defines how instances are distributed and how they upgrade as the standard evolves.

What's in this release

The megabrain specification, v0.2.0 (attached: SPEC.md)

One new normative section — §15 Distribution and upgrades — replacing the fork-based distribution model with a mechanism that works on heavily customized, private instances:

  • The ownership boundary — every file shipped by the standard is either managed (replaced wholesale on upgrade) or instance-owned (touched only where a migration step directs it). AGENTS.md and megabrain.md are managed in structure, instance-owned in content. No merge machinery, no patch programs
  • The lock file — .megabrain/lock.json records the installed version, release, and hash of every managed file as installed. It is the authoritative upgrade anchor, makes drift detection a local comparison, and collapses contract-portability checking into a hash equality test
  • Migration packs — every conformance-changing release ships a MIGRATING.md index plus scripts. Steps are programmatic (idempotent POSIX bash) or agentic (prose executed by the agent), so semantic changes that no patch could express — a renamed status value across all your notes — are still shippable
  • The upgrade procedure — agent-executed by design: clean-tree gate, rollback tag, sequentially applied packs, and wholesale managed-file replacement with drift warnings. Git being mandatory is what makes "replace wholesale" non-destructive
  • The conformance checker — a managed, version-aware script that validates an instance against the spec_version it actually satisfies, reporting violations by requirement identifier. It gates every upgrade before and after, and bisects failed chains
  • Release policy — migration packs are tested against the two preceding minor versions; older chains remain applicable in sequence but are labeled experimental

Upgrading from 0.1.0

The migration pack for 0.1.0 → 0.2.0 — which adds the lock file, the conformance checker, and the upgrade procedure to existing instances — ships with the distribution tooling tracked in the project plan. Until then, 0.2.0 is informational for existing instances: nothing in 0.1.0 content or schema changes.

Full Changelog: v0.1.0...v0.2.0

Assets 3
Loading