tap.config.schema.json describes what a deployment supports: which dimension sets,
which entity types, and which TAP rendering modes. Each deployment ships one *.tap.json
file that validates against this schema.
Structure
dimension_sets
Named groups of dimensions. Each set is active when specific entity type conditions are met.requires_politician_entity: true is a conditional taxonomy (): the
dimension set is only included when at least one entity in the TAP is a politician. This
prevents a voter-vs-voter TAP from loading congressional committee dimensions.
entity_types
Registry of entity types supported by this deployment.tap_modes
Documents which rendering modes this deployment supports.dimension_source (dynamic dimensions)
Instead of fixed dimension sets, a deployment can specify a dynamic source — dimensions derived at render time from closed poll results. Used byseda-haqq/taps/referenda.tap.json:
Deployment configs
| Deployment | File | Dimension sets |
|---|---|---|
| blockchain/ | blockchain/taps/expertise.tap.json | expertise (28 majors), committee (congressional) |
| seda-haqq/ | seda-haqq/taps/referenda.tap.json | dynamic (past referenda) |
| dao/ | dao/taps/dao.tap.json | governance_category (treasury, protocol, security, community, meta) |