The architecture optimization pass is complete for its 0.1.2 scope. Remaining items below are future trains, not unresolved issues in the shipped optimization branch.
1. Current Baseline
HeavenBase now keeps the public agent-facing surface stable while tightening the internals that support it.- The required
systemextension owns Catalog, MetaSchema, Capsule, and Toolkit rows. - The default-loaded
promptextension owns Prompt and Translation rows whilehb.Promptremains the root API. - MCP profiles, serializers, toolkit families, storage profiles, and SQL/database dialect metadata are mirrored into
sys-metaschema. - Optional
agent,memory, anddatabasetools contribute through extension-local toolkit families. - The default test suite focuses on fast integrity coverage; provider and implementation-detail contracts are opt-in.
2. Near-Term Focus
- Keep registry metadata reloads stable without arbitrary import execution from persisted rows.
- Choose the next train: deeper registry persistence or provider-native execution improvements.
- Keep public docs, Chinese translations, and local architecture references synchronized as code moves.
3. Longer-Term Directions
- Full registry convergence over workspace-owned metadata rows.
- Row-data export/import with explicit restore semantics.
- Aggregation operators such as count, min, max, and average through the handler model.
- Parallel query snapshots and richer cross-backend merge policy controls.