Two related additions to schemas/general.json that reduce friction for teams using different terminology.
Type aliases
Extend the type field enum for existing entities to accept common alternative names:
goal entity also accepts "outcome" as a valid type value- Review other entities for obvious aliases (e.g. does
mission need one? Probably not.)
JSON Schema supports this via enum with multiple values or a oneOf pattern.
Fourth-layer entity type
Add a new entity type representing the bottom layer of a discovery tree — the test or probe used to evaluate a solution idea before building.
Accept multiple type aliases to avoid forcing a terminology choice on teams:
"experiment" | "assumption_test" | "test"
Fields:
type (required): one of the aliases abovestatus (required): standard lifecycle enumparent (required): wikilink to a solution nodeassumption (required for status beyond identified): the specific belief being tested — the core of what this entity representscategory (optional): desirability | viability | feasibility | usability | ethical — the Torres taxonomy for assumption types
No other optional fields; extra attributes remain allowed by the schema.
Notes
- The canonical name question (experiment vs assumption_test vs test) is intentionally left open by supporting aliases
- In
strict_ost.json (separate issue), parentage and required fields will be more constrained
- Depends on schema reorganization issue being completed first so shared defs are in place
Relates to #3 (research findings).
Two related additions to
schemas/general.jsonthat reduce friction for teams using different terminology.Type aliases
Extend the
typefield enum for existing entities to accept common alternative names:goalentity also accepts"outcome"as a valid type valuemissionneed one? Probably not.)JSON Schema supports this via
enumwith multiple values or aoneOfpattern.Fourth-layer entity type
Add a new entity type representing the bottom layer of a discovery tree — the test or probe used to evaluate a solution idea before building.
Accept multiple type aliases to avoid forcing a terminology choice on teams:
"experiment"|"assumption_test"|"test"Fields:
type(required): one of the aliases abovestatus(required): standard lifecycle enumparent(required): wikilink to a solution nodeassumption(required for status beyondidentified): the specific belief being tested — the core of what this entity representscategory(optional):desirability | viability | feasibility | usability | ethical— the Torres taxonomy for assumption typesNo other optional fields; extra attributes remain allowed by the schema.
Notes
strict_ost.json(separate issue), parentage and required fields will be more constrainedRelates to #3 (research findings).