Skip to content

schema-pack: declare extract_atoms + synthesize_concepts phases on gbrain-base-v2#2294

Open
viethungvili wants to merge 1 commit into
garrytan:masterfrom
viethungvili:add-atom-concept-phases-to-base-v2
Open

schema-pack: declare extract_atoms + synthesize_concepts phases on gbrain-base-v2#2294
viethungvili wants to merge 1 commit into
garrytan:masterfrom
viethungvili:add-atom-concept-phases-to-base-v2

Conversation

@viethungvili

Copy link
Copy Markdown

Problem

gbrain-base-v2 declares the atom and concept page types, but its phases: list is empty. Since extract_atoms / synthesize_concepts are gated on the active pack's phases:, a base-v2 brain never populates those two types — the taxonomy ships the types but nothing produces them.

The only bundled packs that declare these phases (gbrain-creator / gbrain-everything) extend: gbrain-base (v1), so adopting them means leaving the v2 canonical taxonomy and re-typing the corpus.

Change

Declare the two phases on gbrain-base-v2 itself (one additive block). phases: is additive — the core phases always run — so this only turns on atom extraction + concept synthesis for base-v2 brains, making the canonical taxonomy self-consistent (the types it ships get populated).

Verified

On a live base-v2 brain (≈200 pages), extract_atoms produced real atoms from the corpus and synthesize_concepts ran clean (promotes concepts as atoms accrue across topics/months). I did not run the repo's full test suite locally.

Open question for you

A user pack that merely extends: gbrain-base-v2 does not inherit v2's types — the extends type-merge appears to skip a standalone bundled parent (base-v2 has extends: null). So a thin opt-in extends-pack isn't currently a clean alternative, which is why this declares the phases on base-v2 directly.

If you'd rather keep phases off base-v2 by default (e.g. to avoid the per-cycle LLM cost for users who only want the taxonomy), I'm happy to instead ship a separate opt-in gbrain-base-v2-creator pack + register it — just let me know your preference.


Drafted with Claude Code; verified against a real base-v2 brain.

…rain-base-v2

gbrain-base-v2 declares the `atom` and `concept` page types, but leaves
`phases:` empty — so on a base-v2 brain nothing ever populates those types
(extract_atoms / synthesize_concepts are gated on the active pack's `phases:`
list). The only bundled packs that declare these phases (gbrain-creator /
gbrain-everything) extend the older gbrain-base v1, so adopting them means
leaving the v2 canonical taxonomy.

This declares the two phases on base-v2 itself, making the canonical taxonomy
self-consistent: the types it ships are actually produced. `phases:` is
additive (the core phases always run), so this only turns on atom extraction +
concept synthesis for base-v2 brains.

Verified live on a base-v2 brain: extract_atoms produced real atoms from the
corpus; synthesize_concepts runs clean and promotes concepts as atoms accrue.

Note: a user pack that merely `extends: gbrain-base-v2` does NOT inherit v2's
types (the extends type-merge appears to skip a standalone bundled parent), so
an opt-in extends-pack isn't currently a clean alternative — happy to ship this
as a separate opt-in `gbrain-base-v2-creator` instead if you'd rather phases
stay off base-v2 by default.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
devty added a commit to devty/gbrain that referenced this pull request Jun 20, 2026
…rain-base-v2

Port of garrytan#2294 (viethungvili). Without this phases declaration,
the atom and concept types shipped in base-v2 stay empty because autopilot
gates extract_atoms/synthesize_concepts on the active pack's phases list.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant