Add adjacent models?

[mindsocket]

Driver tree
Landscape (product architecture, wardley map etc) - slippery slope!
JC meta concepts (narrative -> things + relationships, models)
OKRs - support different goal structures

Consider which of these actually help with a core goal. Driver tree helps with expressing and clarifying expected impact. A broad landscape is less clearly useful on an ongoing basis, especially for small-mid sized orgs.

[mindsocket]

Findings from composing a super-schema with Wardley mapping entities

While building a schema that combines OST, knowledge-wiki, and Wardley mapping entity types, two related findings emerged:

1. Local partial $ref by $id works (undocumented)

Co-locating a partial .json file alongside the main schema file causes it to be auto-discovered and registered by its $id. You can then reference it in $ref expressions using that ID:

// _wardley_mapping.json (co-located with main schema)
{ "$id": "local://myspace/_wardley_mapping", "$defs": { "landscape": { ... } } }

// main schema
{ "oneOf": [ { "$ref": "local://myspace/_wardley_mapping#/$defs/landscape" } ] }

This works and shows up correctly in schemas show as a [local] registry entry. It enables local partials as a stepping stone before a definition is bundled. Worth documenting — the skill prompt and schemas show registry output don't currently explain this.

2. Entity types in full schemas can't be composed by reference

The limitation that motivated this comment: you can't $ref into the oneOf entries of a full schema like general.json or knowledge_wiki.json. If you want to build a super-schema that combines entity types from both, you have to copy them inline.

This points to two possible directions (I lean toward the second):

a) Loosen the constraint — allow $ref to resolve into oneOf entries of full schemas at the entity level.

b) Move entity definitions into partials — extract entity type definitions from full schemas into _ost_entities.json, _wiki_entities.json etc., so they can be composed via $ref into new schemas. Full schemas become thin composers. Partials are analogous to abstract types in OO — reusable, composable building blocks.

Option (b) embraces the existing partial convention and would make both local composition and future bundling cleaner. The Wardley mapping work here (with _wardley_mapping.json as a local partial that's a candidate for future bundling) is an example of this pattern in practice.