Exponential Roadmap Initiative logo
Brand Design SystemProject Alignment Tracker

BDS Alignment Tracker

Project Compliance

Live status of BDS alignment across all ERI projects. Data is fetched directly from each project's published bds-meta.json file. Latest @eri/components release: v2.10.6

9Projects tracked
1Compliant
1Needs update
7Violations / unreachable
Refreshed 8:14:49 PM
Compliant
Package:v2.10.6
CSS:✓ dist/

Updated 2026-04-19 · Manus

Needs update
Package:v2.10.6
CSS:✓ dist/
EriContactUsButton — showCTA={false} — this application IS the Contact Us service. A 'Contact Us' button in the header of the contact form itself would be circular. This is the one legitimate exception to showCTA={true} in the BDS. — ref:https://bds.exponentialroadmap.org/#standard-components — approved:ERI design team

Updated 2026-04-19 ·

Planetary Stewardship Monitor
psm.exponentialroadmap.org ↗
Unreachable

Could not fetch bds-meta.json

Unreachable

Could not fetch bds-meta.json

Unreachable

Could not fetch bds-meta.json

Unreachable

Could not fetch bds-meta.json

Unreachable

Could not fetch bds-meta.json

Unreachable

Could not fetch bds-meta.json

Unreachable

Could not fetch bds-meta.json

How this tracker works

Every ERI project must publish a static bds-meta.json file at client/public/bds-meta.json so it is served at https://{domain}/bds-meta.json. The tracker fetches this file from every registered project and renders a live compliance dashboard. Update it whenever you upgrade @eri/components, change the CSS import method, add or fix a component, or resolve a violation.

Canonical template — copy into client/public/bds-meta.json

{ "schemaVersion": "1.0", "project": "your-project-id", "projectName": "Your Project Name", "domain": "your-project.exponentialroadmap.org", "eriComponentsPin": "v2.10.6", "cssImportMethod": "dist", "components": { "EriAppHeader": { "used": true, "compliant": true }, "EriPageLayout": { "used": true, "compliant": true }, "EriHeroSection": { "used": true, "compliant": true }, "EriAppFooter": { "used": true, "compliant": true }, "EriStatusBadge": { "used": true, "compliant": true }, "EriContactUsButton": { "used": true, "compliant": true } }, "knownViolations": [], "overallStatus": "green", "lastUpdated": "2026-04-19", "updatedBy": "Manus" }

Field reference

schemaVersion"1.0"

Always "1.0" — do not change.

project"hal"

Short lowercase project code. Examples: hal, psm, playbook, taxonomy.

projectName"Human-AI Lab"

Full human-readable project name.

domain"hal.exponentialroadmap.org"

Canonical deployed domain (no https://).

eriComponentsPin"v2.10.6"

Exact version tag installed. Latest is v2.10.6.

cssImportMethod"dist"

"dist" = correct. "source-workaround" = amber. "none" = red.

components{ ... }

Per-component status. Each key: { used: boolean, compliant: boolean }.

knownViolations[]

Array of free-text violation strings. Empty array = no violations.

overallStatus"green"

"green" | "amber" | "red". Set manually based on the status rules.

lastUpdated"2026-04-19"

ISO date (YYYY-MM-DD) of last update.

updatedBy"Manus"

Who last updated this file — "Manus" or your name.

Status rules

Compliant — All components compliant, CSS uses dist/, no violations.
Needs update — CSS uses @source workaround, or package pin is 2+ minor versions behind v2.10.6.
Violations — Any component has a known violation, or knownViolations is non-empty.
Unreachable — Project has not yet published a bds-meta.json file, or the URL is unreachable.

Component values guide

used: true, compliant: true

Component is used and follows the BDS spec.

used: true, compliant: false

Component is used but has a known deviation. Add a note to knownViolations.

used: false, compliant: false

Component is not used in this project (e.g. EriContactUsButton on a data-only tool).

Quick checklist before setting overallStatus: "green"

  • ✓ @eri/components pinned to v2.10.6
  • ✓ CSS imported from dist/eri-components.css
  • ✓ All used components have compliant: true
  • ✓ knownViolations is an empty array []
  • ✓ File committed at client/public/bds-meta.json and deployed