bit-config

Configuration shared by every Bit Trading Company Hugging Face Space.

File	What
nav.json	the App Sidebar: modules, launch status, destinations

Why this is a dataset and not code

The Spaces share their chrome through the bit-ui package, pinned per Space as a git submodule. Pinning is right for code — a bad change cannot break every Space at once — but wrong for a link, because promoting a module from coming soon to live would then mean a pull request in every repository.

So the navigation is data instead. Edit nav.json, and each Space picks it up on its next restart.

Editing

Use ops/publish_nav.py in the bit-finance-atlas repo. It validates the document against the same rules the Spaces apply before uploading, and shows a diff first.

Rules

• A live item needs a url. One without is demoted to soon rather than rendered as a dead link.
• Only https, http, mailto and tel URLs are accepted.
• progress is optional and omitted by default. The coming-soon dialog draws a build-progress bar only when a real number is supplied here; an invented percentage is worse than no bar.
• Every value is escaped when rendered. It is still config that reaches every Space at once, so treat it with the care that implies.