Repository navigation
fix-missing-verisim-feed.sh stamps a feed format and destination that do not exist (hexad / feeds/) #640
Description
What is wrong
scripts/fix-missing-verisim-feed.sh stamps a VeriSimDB feed descriptor whose
three data-path values do not exist in VeriSimDB. Every repo this bot "fixes"
inherits them.
Current template block:
repository = "https://github.com/hyperpolymath/nextgen-databases"
data-store = "verisim-data"
...
format = "hexad"
destination = "verisim-data/feeds/"Evidence (checked 2026-11-01)
| Value | Reality | Source |
|---|---|---|
format = "hexad" |
The record schema is the octad (8 modal witnesses). Records carry "schema": "verisimdb.octad.v1". HEXAD survives only as a legacy VCL keyword for the octad source, retained for backward compatibility — a query keyword, not a wire format. |
verisimdb/spec/grammar.ebnf v3.0 (hexad_source = 'HEXAD', uuid, header "Octad (8 modalities)"); verisimdb/README.adoc ("uses HEXAD as the legacy keyword for the octad source (8 modal witnesses)"); verisimdb/.verisimdb/octads/*.json; verisimdb-data/scans/octads/pa-*.json |
destination = "verisim-data/feeds/" |
No feeds/ directory exists in any of the three repos. The store's documented layout is scans/ (flat per-repo results) and scans/octads/ (octad records). |
verisimdb-data/README.adoc §"Layout (by purpose)" |
data-store = "verisim-data" |
The store repo is verisimdb-data. verisim-data does not exist. |
repo listing |
repository = .../nextgen-databases |
nextgen-databases is the research parent (QuandleDB, VeriSimDB, Lithoglyph, …), not the engine. |
its repo description |
Also: the bot writes verisim.a2ml and its idempotency check only skips when
verisim.a2ml exists — so a repo that already carries
.machine_readable/integrations/verisimdb.a2ml (the name most fleet copies use,
e.g. hyperpolymath/echidna, hyperpolymath/nextgen-typing) gets a second
descriptor instead of being left alone.
Affected today
hyperpolymath/echidna/.machine_readable/integrations/verisim.a2ml still carries
format = "hexad". hyperpolymath/nextgen-typing carried the same block until it
was fixed locally in 759a33e/b20c279 (that repo audits its descriptors against
the owning repos and treats a dead path as a defect).
Proposed fix
[integration]
name = "verisimdb"
type = "data-feed"
repository = "https://github.com/hyperpolymath/verisimdb"
parent = "https://github.com/hyperpolymath/nextgen-databases"
data-store = "verisimdb-data"
[feed-config]
emit-scan-results = true
emit-build-metrics = true
emit-dependency-graph = true
# The record schema is the octad (8 modal witnesses). "HEXAD" is a legacy VCL
# keyword, not a wire format.
format = "verisimdb.octad.v1"
destination = "verisimdb-data/scans/octads/"plus: write verisimdb.a2ml, and make the idempotency check skip when either
filename exists.
If the intent is instead that consumers emit the flat per-repo scan result
(scans/<repo>.json, per the store README's "File format"), then format should
name that schema and destination should be verisimdb-data/scans/ — either
way, hexad and feeds/ are not options.
Found while auditing cross-repo descriptors in hyperpolymath/nextgen-typing
(item 5 of a documentation/proof consistency audit).
Activity